Systems and visualization interfaces for display of space object imagery

ABSTRACT

The system is configured to generate a display comprising a longitude-time graph comprising. The longitude-time graph may include a longitude axis spanning from a lower-longitude limit to an upper-longitude limit, a time axis spanning from a lower-time limit to an upper-time limit and a plurality of pixels corresponding to longitude-time points within the longitude-time graph, each of the plurality of longitude-time points corresponding to a set of identifiers having a time identifier between the lower-time limit and the upper-time limit and having a longitude identifier between the lower-longitude limit and the upper-longitude limit. In response to a user selection of a time identifier and a name identifier, the system can generate a display of at least one of the plurality of photographs.

INCORPORATION BY REFERENCE OF RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/280,967, filed Feb. 20, 2019. This application also claims thebenefit under 35 U.S.C. § 119(e) of U.S. Provisional Patent ApplicationNo. 62/634,765, filed Feb. 23, 2018 and 62/800,964, filed Feb. 4, 2019.The entire contents of these applications are incorporated by referenceand made a part of this specification.

BACKGROUND

Field

This disclosure relates generally to tracking space objects such assatellites and visual interfaces and computer configurations used insuch tracking.

Description of Related Art

Visualization interfaces can be used to allow a user to view,manipulate, and adjust data representing tracked orbital objects (e.g.,satellites). Tracking orbital objects involves taking in an amount ofdata and incorporating that data into a workable and usable interface.

Tracking orbital objects may be done using photographs of objects inspace and tracking their positions using a plurality of photographs.Visualization systems have been developed in various fields that providesome functionality with regard to portraying various information.However, many features are lacking and many problems exist in the artfor which this application provides solutions.

SUMMARY

Example embodiments described herein have innovative features, no singleone of which is indispensable or solely responsible for their desirableattributes. Without limiting the scope of the claims, some of theadvantageous features will now be summarized.

In some embodiments, a system for displaying image data derived fromphotographs of objects in orbit around a planet, can include a computerreadable storage configured to communicate instructions for displaying aplurality of graphs. The system can also include a hardware processor incommunication with the computer-readable storage. The instructions, whenexecuted by the hardware processor, are configured to cause the systemto receive image data derived from a plurality of photographs of objectsin orbit around the planet and receive a plurality of sets ofidentifiers. Each of the sets may be associated with a photograph. Thesystem may receive a plurality of identifiers of each set derived fromthe associated photograph, wherein each set of identifiers correspondsto an object in orbit and may include a name identifier, a timeidentifier, a latitude identifier, a longitude identifier and a scalaridentifier.

The system is also configured to generate a display comprising alongitude-time graph comprising. The longitude-time graph may include alongitude axis spanning from a lower-longitude limit to anupper-longitude limit, a time axis spanning from a lower-time limit toan upper-time limit and a plurality of pixels corresponding tolongitude-time points within the longitude-time graph. Each of theplurality of longitude-time points can correspond to a set ofidentifiers having a time identifier between the lower-time limit andthe upper-time limit and having a longitude identifier between thelower-longitude limit and the upper-longitude limit. The instructions,when executed by the hardware processor, are configured to cause thesystem to, in response to a user selection of a time identifier and aname identifier, generate a display of at least one of the plurality ofphotographs.

BRIEF DESCRIPTION OF THE DRAWINGS

The following drawings and the associated descriptions are provided toillustrate embodiments of the present disclosure and do not limit thescope of the claims.

FIG. 1A schematically shows a network configuration that allows for thepassing of data to a visualization system.

FIG. 1B shows a schematic of an example visualization display.

FIG. 2 shows an example visualization display with a longitude-timegraph, scalar-time graph, a longitude-latitude graph, and a displayarea.

FIG. 3 shows a detail view of an example longitude-time graph that maybe a part of the visualization display described in FIG. 2.

FIG. 4 shows a detail view of an example longitude-latitude graph thatmay be a part of the visualization display described in FIG. 2.

FIG. 5 shows a detail view of an example scalar-time graph that may be apart of the visualization display described in FIG. 2.

FIG. 6 shows a zoomed-in and panned view of the visualization display ofFIG. 2.

FIG. 7 shows the same view as FIG. 6 after the first longitude axis andthe synchronized second longitude axis have been zoomed in.

FIG. 8 shows the same view as FIG. 7 after the first time axis and thesynchronized second time axis have been zoomed in.

FIG. 9 shows a zoomed-in and panned view of a longitude-time graph andscalar-time graph at a current time horizon.

FIG. 10A shows a tagging interface comprising a stitching tool interfaceand an analysis plot interface.

FIG. 10B shows a selection by a user of a collection of firstlongitude-time source points.

FIG. 10C shows a selection by a user of a collection of secondlongitude-time source points.

FIG. 10D shows the visualization display of FIG. 10C after a user hasselected the stitch selector.

FIG. 11 shows an example visualization display with a longitude-timegraph, scalar-time graph, a longitude-latitude graph, and a displayarea.

FIG. 12 shows a zoomed-in and panned view of a portion of thelongitude-time graph of FIG. 11.

FIG. 13 shows the same view as FIG. 12 after the first longitude axisand the synchronized second longitude axis have been zoomed in.

FIG. 14 shows the same view as FIG. 13 after the first time axis and thesynchronized second time axis have been zoomed in.

FIG. 15 shows a zoomed-in and panned view of a longitude-time graph at acurrent time horizon.

FIG. 16 shows a tagging interface comprising a stitching tool interfaceand an analysis plot interface.

FIG. 17 shows a selection by a user of a collection of firstlongitude-time source points.

FIG. 18 shows a selection by a user of a collection of secondlongitude-time source points.

FIG. 19 shows the visualization display of FIG. 18 after a user hasselected the stitch selector.

FIG. 20 shows a representation of an orbit of a space objectsuperimposed on a longitude-time graph and longitude-latitude graph.

FIG. 21 shows the visualization display of FIG. 20 with highlightedlongitude-time points and longitude-latitude points indicating aselection of multiple tracks associated with a space object.

FIG. 22 shows a visualization display comprising a photograph selectedfrom a set of photographs based on a specified latitude range, aspecified longitude range, and a specified time range.

FIG. 23 shows the visualization display of FIG. 22 comprising aphotograph modified relative to the photograph shown in FIG. 22.

FIG. 24 shows a visualization display comprising an indication of auser-selected primary object in a photograph.

FIG. 25 shows a visualization display comprising an indication of asecondary object detected by a space object detection system.

FIG. 26 shows a visualization display comprising a plurality of tracksselected by a user.

FIG. 27 shows a visualization display comprising an orbit of a spaceobject determined using a destination track and source tracks.

FIG. 28 shows a visualization display comprising longitude, time, andselected track labels.

FIG. 29 shows a visualization display comprising selected tracks of aspace object, an orbit for the space object, and a graph of residualsbetween the selected tracks and the orbit.

These and other features will now be described with reference to thedrawings summarized above. The drawings and the associated descriptionsare provided to illustrate embodiments and not to limit the scope of anyclaim. Throughout the drawings, reference numbers may be reused toindicate correspondence between referenced elements. In addition, whereapplicable, the first one or two digits of a reference numeral for anelement can frequently indicate the figure number in which the elementfirst appears.

DETAILED DESCRIPTION

Although certain embodiments and examples are disclosed below, inventivesubject matter extends beyond the specifically disclosed embodiments toother alternative embodiments and/or uses and to modifications andequivalents thereof. Thus, the scope of the claims appended hereto isnot limited by any of the particular embodiments described below. Forexample, in any method or process disclosed herein, the acts oroperations of the method or process may be performed in any suitablesequence and are not necessarily limited to any particular disclosedsequence. Various operations may be described as multiple discreteoperations in turn, in a manner that may be helpful in understandingcertain embodiments; however, the order of description should not beconstrued to imply that these operations are order dependent.Additionally, the structures, systems, and/or devices described hereinmay be embodied as integrated components or as separate components. Forpurposes of comparing various embodiments, certain aspects andadvantages of these embodiments are described. Not necessarily all suchaspects or advantages are achieved by any particular embodiment. Thus,for example, various embodiments may be carried out in a manner thatachieves or optimizes one advantage or group of advantages as taughtherein without necessarily achieving other aspects or advantages as mayalso be taught or suggested herein.

Described herein are methodologies and related systems for visualizingdata from tracked satellites and other space objects. It will beunderstood that although the description herein is in the context ofsatellites, one or more features of the present disclosure can also beimplemented in tracking objects other than satellites like, for example,aircraft, watercraft, projectiles, and other objects. Some embodimentsof the methodologies and related systems disclosed herein can be usedwith various tracking systems, including, for example, those based ongovernment databases.

Unless explicitly indicated otherwise, terms as used herein will beunderstood to imply their customary and ordinary meaning.

Disclosed herein are methods and systems relating generally to thetracking of objects in orbit (e.g., satellites), other space objects,and related systems and methods of providing an interactive userinterface to interact with data related to the tracking of theseobjects. The information therein can be stored in one or more databases.

Tracking objects in orbit and other space objects can include receivingimage data (e.g., photographs) of portions of the sky from one or moretelescopes positioned at various positions across the globe. Thephotograph data can be used to map out the entirety or near entirety ofthe sky. Various altitudes above sea level may be tracked. The data canbe tracked and processed in real-time. For example, a contemporarydatabase may be configured to receive real-time image data. A historicaldatabase may be configured to store data received before a thresholdtime. The threshold time may be a specified amount of time (e.g., years,months, days, etc.). Alternatively, the threshold time may refer to atime based on a user action. For example, the historical database may beconfigured to store data received before a user causes the system todisplay the user interface. Using an algorithm, the received data may beconsolidated and categorized. For example, the algorithm may beconfigured to determine whether objects that appear in a plurality ofphotographs correspond to the same object over time and space.

FIG. 1A is an example network configuration 194 for a visualizationsystem 190. The architecture of the visualization system 190 can includean arrangement of computer hardware and software components used toimplement aspects of the present disclosure. The visualization system190 may include more or fewer elements than those shown in FIG. 1A. Itis not necessary, however, that all of these elements be shown in orderto provide an enabling disclosure. In some embodiments, thevisualization system 190 is an example of what may be referred to underdifferent names.

As illustrated, the visualization system 190 can include a hardwareprocessor 188, a memory 146, a real-time orbital object data interface172, a tagging interface 174, a image interface 176, a real-timeconnection interface 178, and/or an real-time connection interface 178,each of which can communicate with one another by way of a communicationbus 142 or any other data communication technique. The hardwareprocessor 188 can read and write to the memory 146 and can provideoutput information for the visualization display 100. The real-timeorbital object data interface 172, tagging interface 174, imageinterface 176, and/or real-time connection interface 178 can beconfigured to accept input from an input device 164, such as a keyboard,mouse, digital pen, microphone, touch screen, gesture recognitionsystem, voice recognition system, and/or another input device capable ofreceiving user input. In some embodiments, the visualization display 100and the input device 164 can have the same form factor and share someresources, such as in a touch screen-enabled display.

In some embodiments, the real-time orbital object data interface 172,the tagging interface 174, the image interface 176, and/or the real-timeconnection interface 178 can be connected to a historical data server140, a contemporary data server 150, and/or a metadata server 154 viaone or more networks 144 (such as the Internet, 3G/Wi-Fi/LTE/5Gnetworks, satellite networks, etc.). The real-time orbital object datainterface 172 can receive graphical data information related to orbitalobjects via the network 144 (the network 144 can provide one-waycommunication or two-way communication). In some embodiments, thereal-time orbital object data interface 172 may receive, whereapplicable, object data information or information that can be used forlocation determination (such as a cellular and/or Wi-Fi signal that canbe used to triangulate a location) and determine the position of one ormore objects.

The tagging interface 174 can receive tagging data from a user via theinput/output device interface 182. The metadata server 154 can providean application programming interface (API) that the tagging interface174 can access via the network 144 (such as, for example, a 3G, Wi-Fi,LTE, or similar cellular network). The metadata server 154 may comprisedata from one or more third-party providers. For example, the metadataserver 154 may comprise government information (e.g., received from aUnited States Air Force satellite database). The image interface 176 mayreceive track information (such as, for example, an ordered list ofknown location coordinates) from a historical data server 140,contemporary data server 150, and/or metadata server 154 via the network144. The track information can also include track-related information,such as photos, videos, or other data related to orbiting objects. Insome embodiments, instead of receiving the track information over anetwork 144 from a historical data server 140, the system can receivesuch track information from a user via a computer-readable storagedevice, such as, for example, a USB thumb drive. The image interface 176can also receive images (e.g., photographs, video) from a contemporarydata server 150. In some embodiments, the map data can providelongitude, latitude, altitude information, and any other informationrelated to orbiting objects.

The memory 146 can contain computer program instructions (grouped asmodules or components in some embodiments) that the hardware processor188 can execute in order to implement one or more embodiments describedherein. The memory 146 can generally include RAM, ROM and/or otherpersistent, auxiliary or non-transitory computer-readable media. Thememory 146 can store an operating system 122 that provides computerprogram instructions for use by the hardware processor 188 in thegeneral administration and operation of the visualization system 190.

The memory 146 can include computer program instructions and otherinformation for implementing aspects of the present disclosure includinga graphic module 124, a tagging module 126, a data integration module128, a synchronization module 130, a user settings module 132, othermodules, and/or any combination of modules.

In some embodiment, the memory 146 may include the graphic module 124that generates a track from the received ordered list of known locationsusing algorithms, such as interpolation or extrapolation algorithms.Additionally, the graphic module 124 may, in response to a userdetermination, alter the format (e.g., axes, labels, values) of thegraphical display. Examples of functionality implemented by the graphicmodule 124 are more fully described, for example, with reference toFIGS. 1A-5.

In some embodiments, the memory 146 includes a tagging module 126 thatthe hardware processor 188 executes in order update, in response to auser action, aspects (e.g., metadata, values) of the underlying data.Accordingly, the tagging module 126 can provide data (e.g., updates) tothe synchronization module 130. Examples of functionality implemented bythe tagging module 126 are more fully described, for example, withreference to FIGS. 10A-10D. The data integration module 128 cancorrelate various data automatically or in response to a user input. Forexample, the data integration module 128 can combine data from the oneor more servers (e.g., the historical data server 140, the contemporarydata server 150, and the metadata server 154) that may be used fordisplaying on the visualization display 100. Examples of functionalityimplemented by the data integration module 128 are more fully described,for example, with reference to FIGS. 2-9.

In some embodiments, the memory 146 includes a synchronization module130 that can be configured to correlate various aspects of data from theone or more servers. For example, the synchronization module 130 can beconfigured to synchronize the display of a data set on multiple graphsor to synchronize elements (e.g., axes, labels, dimensions, alignments,etc.) of one or more graphs of the visualization display 100. Thesynchronization module 130 can update data based on inputs from thetagging module 126 (such as stitched objects or elements), guidanceparameters from the user settings module 132, and/or inputs from thedata integration module 128. Examples of functionality implemented bythe synchronization module 130 are more fully described, for example,with reference to FIGS. 2-9.

In some embodiments, the memory 146 includes a user settings module 132.The user settings module 132 can provide access to various user settingsrelated to user preferences, including graph parameters, graphconfigurations (e.g., layout, orientation, formatting, etc.) and modes(e.g., display mode, tag mode, etc.). For example, the threshold valuesused for determination of the direction guidance mode may be accessedthrough the user settings module 132. In some instances, the usersettings module 132 may provide connectivity to a data store 168 andaccess user settings from or store user settings to the data store 168.Examples of functionality implemented by the user settings module 132are more fully described, for example, with reference to FIGS. 2-10D. Insome embodiments, other interfaces and modules, such as the real-timeorbital object data interface 172, the tagging interface 174, the imageinterface 176, real-time connection interface 178, and/or input/outputdevice interface 182 may have access to the data store 168.

The historical data server 140 may communicate via the network 144 witha historical data interface. The historical data interface may includeone or more of the real-time orbital object data interface 172, thetagging interface 174, the image interface 176, and the real-timeconnection interface 178. The historical data interface may beconfigured to receive historical data of objects in orbit around aplanet from a historical data set. The historical data may comprise atime, a latitude, a longitude, a scalar, and/or an object identifier(e.g., name) for each object. The historical data can comprise datacollected over a period of time greater than a threshold time (e.g., ayear).

The amount of historical data can be unusually immense. For example, theamount of historical data may include billions of data identifiersderived from petabytes or even exabytes of photographic data. Thehistorical data obtained may be increasing over time. Such an immenseamount of data can cause serious challenges related to, for example,maintaining, sorting, extracting, transmitting, and/or displaying thatdata, particularly in a timely and organized fashion. This data may besupplemented from other databases (e.g., the metadata server 154), suchas third-party databases. Such third-party databases may includegovernment organizations, such as military groups (e.g., the UnitedStates Air Force), but may include private (e.g., commercial) sourcesadditionally or alternatively.

The contemporary data server 150 may communicate via the network 144with a real-time (e.g., contemporary) data interface configured toreceive contemporary data of objects in orbit around a planet from acontemporary data set. The contemporary data may comprise a time, alatitude, a longitude, an object identifier, and/or a scalar for eachobject. The contemporary data may comprise data collected after thehistorical data available from the historical data set. The contemporarydata may include data received within a few minutes or even seconds of acurrent time. The contemporary data may be data stored after a user hasinitiated a particular action, such as causing the system to generate avisualization display 100. In such a case, the system can be configuredto update the visualization display 100 with pixels associated with thedata collected after the generation of the visualization display 100.

FIG. 1B shows a schematic of an example visualization display 100. Sucha visualization display 100 may operate within the network configuration194 of FIG. 1A, for example. The visualization display 100 may bedisplayed on any type of digital display device, such as a desktopcomputer, a laptop computer, a projection-style device, a smartphone, atablet, a wearable device, or any other display device. Thevisualization display 100 may include a first plot 104, a second plot108, a third plot 112, and/or a display area 116.

The first plot 104 and second plot 108 may be displayed with similar(e.g., within a few pixels) vertical dimensions and/or similar verticalalignment. For example, the first plot 104 may be disposed directly leftof the second plot 108. The third plot 112 may have similar verticaldimensions and/or similar vertical alignment as the display area 116.The first plot 104 may have similar horizontal dimensions and/or similarhorizontal alignment as the third plot 112. In some embodiments, thesecond plot 108 may have similar horizontal dimensions and/or similarhorizontal alignment as the display area 116. In some designs, thesecond plot 108 may include a tagging interface (e.g., a stitchingand/or splicing interface).

FIG. 2 shows an example visualization display 200 with a longitude-timegraph 204, scalar-time graph 208, a longitude-latitude graph 212, and adisplay area 216. The visualization display 200 may correspond in someor all respects with the visualization display 100 of FIG. 1B. FIGS. 3-5may provide further details related to one or more portions of FIG. 2.

The visualization display 200 can include a longitude-time graph area228. In some embodiments, the longitude-time graph area 228 is boundedby a first longitude axis 224 and a first time axis 220. Each of thefirst longitude axis 224 and/or first time axis 220 can include one ormore axis labels. In some designs, the axis labels of the firstlongitude axis 224 are not shown in relation to the longitude-time graph204 but in relation only to, for example, the longitude-latitude graph212 (see, e.g., FIGS. 10A-10D). The axis labels of the first longitudeaxis 224 and/or first time axis 220 may be equidistant from one anotherto portray equal intervals of the respective longitude or time. Thefirst longitude axis 224 may span any portion of longitudes found on aplanet (e.g., Earth). For Earth, the range may be from 180 W (e.g., 180°West or −180°) to 180 E (e.g., 180° East or +180°) or any range therein.For example, as shown in FIG. 2, the first longitude axis 224 spans from180 W to 120 E. However, other ranges are possible, examples of whichare described below. The first longitude axis 224 may run eastern-mostto western-most from left to right (e.g., as shown in FIG. 2), but otherconfigurations are possible.

The first time axis 220 may span any time from a historical time tonearly a current time of a user. For example, as shown by FIG. 2, thefirst time axis 220 may span from 2014-7 (e.g., July 2014) to 2017-07(e.g., July 2017). The displayed time may correspond to a universaltime, such as the coordinated universal time (UTC). Stored time valuesmay similarly be in UTC. The latest time may be labeled “current time,”“now,” or a similar label and/or may indicate to a user that data fromthe most current time available are displayed. The most current timeavailable may include time within a few seconds (e.g., 1-60 seconds) ora few minutes (e.g., 1-30 minutes) of a present time at which a vieweris observing the data. The first time axis 220 may span from ahistorical time from an earliest time when a database (e.g., ahistorical data server 140, a miscellaneous data server 154) hasavailable data. The earliest time when the database has data may be asfar back as the year 2010. In some embodiments, the historical dataserver 140, the contemporary data server 150, and/or the metadata server154, may be configured to store some or all of the corresponding data inshort-term memory storage (e.g., Random Access Memory (RAM)). The firsttime axis 220 may include axis labels that run earliest to most recentfrom top to bottom (e.g., as shown in FIG. 2), but other variations arepossible. Axis labels may be spaced equidistant from each other toindicate equal time intervals therebetween. An axis label may show acorresponding time to include a year, a month, a day, an hour, a minute,and/or a second, depending on the level of specificity that isavailable, the span of the first time axis 220, and/or the level ofdetail that is needed for a particular display. As shown in FIG. 2, eachaxis label may not include superfluous detail (e.g., not show a year ateach interval) in order to reduce clutter and to increase clarity for aviewer.

Each axis label of the first longitude axis 224 and/or first time axis220 may include gridlines. For example, the longitude-time graph 204 mayinclude one or more horizontal gridlines 296 and/or vertical gridlines294 (not shown in FIG. 2). The vertical gridlines 294 and horizontalgridlines 296 may aid a viewer in identifying a particular point withinone or more of the graphs. To further aid a user in visualizing theorbital object information, in some embodiments, the longitude-timegraph 204 may display a longitude-time map (not shown in FIG. 2). Thelongitude-time map may be a geographical map of a portion of the planet.For example, the longitude-time map may identify the contours and/orlimits of various landmasses (e.g., continents, islands). Thisinformation may help a user quickly ascertain over which landmass orbody of water, for example, an orbital object may be located. Forexample, it may be useful to a viewer to see that a satellite orbitsabove a portion of Africa (or other planetary location). Pointsdisplayed on the corresponding graph (e.g., the longitude-time graph204) may be superimposed over the geographic map (e.g., thelongitude-time map).

The longitude-latitude graph 212 may include a longitude-latitude grapharea 240 that is bounded by a second longitude axis 236 and a latitudeaxis 232. Each of the second longitude axis 236 and/or the latitude axis232 can include one or more axis labels. The second longitude axis 236and the first longitude axis 224 may be identical. For example, firstlongitude axis 224 may respond to a user input in the same way as thesecond longitude axis 236. In some embodiments, the axis labels of thesecond longitude axis 236 represent the values of the axis labels forthe longitude-time graph 204. The axis labels of the second longitudeaxis 236 and/or the latitude axis 232 may be equidistant from oneanother to portray equal intervals of the respective longitude orlatitude Like the first longitude axis 224, the second longitude axis236 may span any portion of longitudes found on the planet. For example,as shown in FIG. 2, the second longitude axis 236 spans from 180 W to120 E. However, other ranges are possible Like the first longitude axis224, the second longitude axis 236 may run eastern-most to western-mostfrom left to right (e.g., as shown in FIG. 2), but other configurationsare possible.

The latitude axis 232 may span any latitude found on the planet. Forexample, the latitude axis 232 may span from 90 S (e.g., 90° South) to90 N (e.g., 90° North) or any range therein. For example, as shown inFIG. 2, the latitude axis 232 may range from 15 S (e.g., 15° South) to15 N (e.g., 15° North). The latitude axis 232 may include axis labelsthat run western-most to eastern-most from left to right (e.g., as shownin FIG. 2), but other variations are possible. Axis labels may be spacedequidistant from each other to indicate equal latitude intervalstherebetween.

Each axis label of the first longitude axis 224 and/or latitude axis 232may include gridlines. For example, the longitude-latitude graph 212 mayinclude one or more horizontal gridlines 296 and/or vertical gridlines294. In some designs, the vertical gridlines 294 may correspond togridlines found in the longitude-time graph 204. If the first longitudeaxis 224 and the second longitude axis 236 span the same values, thenthe same vertical gridlines 294 may appear to run through both thelongitude-time graph 204 and the longitude-latitude graph 212. In someembodiments, the longitude-latitude graph 212 may display alongitude-latitude map. In some designs, the longitude-latitude map mayinclude a portion of the same features in the longitude-time map. Thelongitude-latitude map may be a geographical map of a portion of theplanet. For example, the longitude-latitude map may identify thecontours and/or limits of various landmasses (e.g., continents,islands). This information may help a user quickly ascertain over whichlandmass or body of water, for example, an orbital object may belocated. For example, it may be useful to a viewer to see that asatellite orbits above a portion of Africa (or other planetarylocation). Points displayed on the corresponding graph (e.g., thelongitude-latitude graph 212) may be superimposed over the geographicmap (e.g., the longitude-latitude map).

The scalar-time graph 208 may include a scalar-time graph area 252 thatis bounded by a scalar axis 248 and a second time axis 244. Each of thescalar axis 248 and/or the second time axis 244 can include one or moreaxis labels. The second time axis 244 and the first time axis 220 may beidentical. For example, first time axis 220 may respond to a user inputin the same way as the second time axis 244. In some embodiments, theaxis labels of the first time axis 220 represent the values of the axislabels for the scalar-time graph 208. The axis labels of the scalar axis248 and/or the second time axis 244 may be equidistant from one anotherto portray equal intervals of the respective longitude or latitude. Likethe first time axis 220, the second time axis 244 may span any time froma historical time to nearly a current time of a user. Additional detailson the historical and (nearly) current times are discussed above inregard to the longitude-time graph 204.

Like the first time axis 220, the second time axis 244 may include axislabels that run earliest to most recent from top to bottom (e.g., asshown in FIG. 2), but other variations are possible. Axis labels may bespaced equidistant from each other to indicate equal time intervalstherebetween. An axis label may show a corresponding time to include ayear, a month, a day, an hour, a minute, and/or a second, depending onthe level of specificity that is available, the span of the first timeaxis 220, and/or the level of detail that is needed for a particulardisplay. As shown in FIG. 2, each axis label may not include superfluousdetail (e.g., not show a year at each interval) in order to reduceclutter and to increase clarity for a viewer.

The scalar axis 248 may span any value of scalars associated withscalars within a database. Each scalar displayed may correspond to amagnitude or other value. For example, the magnitude may represent anintensity (e.g., of light from the orbital object). However, otherscalar values are also possible, such as a size, a projected area, atemperature, a mass, a radar cross section, an altitude, an inclination,a delta-V, a time until a certain event, a probability of a certainevent, etc. Many variants are possible. The scalar axis 248 may includeaxis labels that run greatest to smallest from left to right (e.g., asshown in FIG. 2), but other variations are possible. Axis labels may bespaced equidistant from each other to indicate equal scalar intervalstherebetween.

Each axis label of the scalar axis 248 and/or the second time axis 244may include gridlines. For example, the scalar-time graph 208 mayinclude one or more horizontal gridlines 296 and/or vertical gridlines294. In some designs, the horizontal gridlines 296 may correspond togridlines found in the longitude-time graph 204. If the first time axis220 and the second time axis 244 span the same values, then the samehorizontal gridlines 296 may appear to run through both thelongitude-time graph 204 and the scalar-time graph 208.

The visualization display 200 may further include a display area 216.The display area 216 may be configured to display an image chip 268.This may offer a viewer an opportunity to see an underlying photographfrom which image data were extracted that correspond to a set of data oridentifiers that are associated with one or more points displayed by thevisualization display 200. The image chip 268 may correspond to aphotograph of one or more orbital objects. For example, the image chip268 may be a representation of the photograph. In some cases, the imagechip 268 may display an object image 270 that represents an orbitalobject. The image chip 268 may include multiple object images 270 (e.g.,sequential images, summated images (see below), etc.). The display area216 may also include an interface toggle 266, which is described in moredetail below.

The visualization display 200 may further include a point marker 256.The point marker 256 may be used to identify a pixel associated with oneor more points (e.g., longitude-time points) indicated by a user withinthe display currently. For example, the point marker 256 may comprise ahighlighted pixel (or cluster of pixels around the highlighted pixel) toidentify the current pixel/point. The one or more points displayed bythe visualization display 200 may be received from one or more databases(e.g., the historical data server 140, the contemporary data server 150,the metadata server 154) via one or more data interfaces (e.g., thereal-time orbital object data interface 172, the tagging interface 174,the image interface 176, the real-time connection interface 178). Thedata interfaces may be referred to as application program interfaces(e.g., APIs). The user may use an input device (e.g., a keyboard, amouse, a digital pen, a microphone, a touch screen, etc.) to indicatethe currently identified pixel. The point marker 256 may further beindicated by a horizontal tracking line 260 and/or vertical trackingline 264. As shown in FIG. 2, each of the horizontal tracking line 260and vertical tracking line 264 may be visible in multiple graphs. Forexample, if the point marker 256 is displayed in the longitude-timegraph 204, the horizontal tracking line 260 may be displayed in both thelongitude-time graph 204 and the scalar-time graph 208. Similarly, thevertical tracking line 264 may be visible in both the longitude-timegraph 204 and the longitude-latitude graph 212.

The point marker 256 may be associated with one or more point markermetadata stamps. The one or more point marker metadata stamps maydisplay one or more data types not evident from a graph in which thepoint marker 256 is currently displayed. For example, in thelongitude-time graph 204, a scalar stamp 274 and/or object identifierstamp 282 may be displayed. This may be because the longitude-time graph204 is not configured to display scalar and/or object identifierinformation. Similarly, a time value, scalar value, and/or objectidentifier may be displayed for an identified pixel within thelongitude-latitude graph 212. Moreover, a longitude value, latitudevalue, and/or object identifier may be displayed for an identified pixelwithin the scalar-time graph 208. As shown in FIG. 2, the scalar stamp274 and/or object identifier stamp 282 may be displayed near (e.g.,within a few pixels of) the point marker 256. The scalar stamp 274 candisplay a scalar value corresponding to a point associated with theidentified (e.g., highlighted) pixel. As shown, the scalar value couldbe, for example, “12.1 VMag.” Similarly, the object identifier stamp 282may display an object identifier (e.g., object name) corresponding tothe point associated with the identified pixel. As shown, the objectidentifier could be, for example, 27820:11003 (AMC-9 (GE-12)). In someembodiments, as noted above, a latitude stamp (not shown) can bedisplayed. The latitude stamp may be displayed near the point marker 256and may display a latitude value corresponding to the point associatedwith the identified pixel.

One or more of the horizontal tracking line 260 and/or the verticaltracking line 264 may have corresponding tracking line metadata stamps.The one or more tracking line metadata stamps may correspond to datatypes displayed by the corresponding graph in which the identified pixelis displayed. For example, as shown in FIG. 2, an identified pixelwithin the longitude-time graph 204 may include a horizontal trackingline 260 and/or the vertical tracking line 264 that correspond,respectively, to a tracking line time stamp 298 and/or a tracking linelongitude stamp 290. Similarly, an identified pixel within thelongitude-latitude graph 212 may include a horizontal tracking line 260and/or vertical tracking line stamp 290 that correspond, respectively,to a tracking line latitude stamp and/or a tracking line longitude stamp290. Moreover, an identified pixel within the scalar-time graph 208 maycorrespond to a horizontal tracking line 260 and/or vertical trackingline stamp 290 that correspond, respectively, to a tracking line timestamp and/or a tracking line scalar stamp. In this way, a user canquickly identify one or more values associated with the pixel identifiedby the point marker 256. The horizontal tracking line stamp (e.g.,tracking line time stamp 298) and/or the vertical tracking line stamp(e.g., tracking line longitude stamp 290) may be displayed near thecorresponding tracking line.

As shown in FIG. 2, the longitude-time graph 204 may include one or moreunhighlighted collections 272 of longitude-time points, highlightedcollections 276 of longitude-time points, and/or selected collections280 of longitude-time points. Similarly, the longitude-latitude graph212 may include one or more unhighlighted collections 284 oflongitude-latitude points, highlighted collections 288 oflongitude-latitude points, and/or selected collections 292 oflongitude-latitude points. Moreover, the scalar-time graph 208 mayinclude various scalar-time points 254 within the scalar-time graph area252. The scalar-time points 254 may include points that are highlighted,unhighlighted, and/or selected.

Object Tracking

The visualization display 200 described herein can be used to trackorbital objects and present that data to a user/viewer in a meaningfulway. The systems displayed herein provide a novel way of presentinghigh-dimensional (e.g., four-dimensional, five-dimensional, or higherdimensional) data in a way that is understandable by a human viewer.

For additional detail related to FIG. 2, reference will now includereference to FIGS. 3-5. FIG. 3 shows a detail view of an examplelongitude-time graph 204 that may be a part of the visualization display200 described in FIG. 2. The first longitude axis 224 may span from alower-longitude limit 312 to an upper-longitude limit 316. Similarly,the first time axis 220 may span from a lower-time limit 304 to anupper-time limit 308. Within the longitude-time graph area 228, thevisualization display 200 may include one or more sets of longitude-timepoints. The one or more sets of longitude-time points may correspond toone or more pixels. Each set of longitude-time points may correspond todata on one or more orbital objects around the planet. For example, eachof the one or more longitude-time points may correspond to a data setcomprising historical data and/or contemporary data. Each set oflongitude-time points may correspond to a set of identifiers. The set ofidentifiers may include a longitude value, a latitude value, a timevalue, a scalar value, and/or an object (e.g., name) identifier. Eachset of identifiers may be obtained from one or more photographs. Thephotographs may contain image data from which one or more identifiers ofthe set of identifiers can be obtained (e.g., through algorithm).

The longitude-time points displayed within the longitude-time graph area228 may be points that have a time value between the lower-time limit304 and the upper-time limit 308. Additionally or alternatively, thedisplayed longitude-time points may have a longitude value between thelower-longitude limit 312 and the upper-longitude limit 316.

As shown in FIG. 3, the point marker 256 may comprise one or morehighlighted pixels that can help a user determine which pixel isidentified by a user input device. If the pixel is associated withobject data, the scalar stamp 274 and/or object identifier stamp 282 maybe displayed within the longitude-time graph area 228. One or both ofthe scalar stamp 274 and the object identifier stamp 282 may bedisplayed in an area easily associated with the point marker 256. If theidentified pixel does not contain corresponding object data, then therespective scalar stamp 274 and/or object identifier stamp 282 may notbe displayed. As shown the pixel currently identified by the pointmarker 256 is a pixel that includes a selected collection 280 oflongitude-time points.

In order to further aid a user, an interface toggle 320 may be includedin the longitude-time graph 204. The interface toggle 320 may bemanipulated by a user from an input device (e.g., function keys on akeyboard, a mouse, etc.). The interface toggle 320 may communicate withthe user settings module 132 (see FIG. 1A) to determine, for example,display settings for the longitude-time graph 204. A user may be able toadjust the display settings using the interface toggle 320. For example,the user may be able to click a box to switch a view type. The user maybe able to filter what types of points (e.g., unhighlighted,highlighted, selected) are displayed. The interface toggle 320 may allowa user to toggle the display of the longitude-time map on and off. Forexample, as shown in FIG. 3, the longitude-time map is toggled off whilein FIG. 2 it is toggled on.

FIG. 4 shows a detail view of an example longitude-latitude graph 212that may be a part of the visualization display 200 described in FIG. 2.The second longitude axis 236 may span from a lower-longitude limit 412to an upper-longitude limit 416. Similarly, the latitude axis 232 mayspan from a lower-latitude limit 408 to an upper-latitude limit 404. Thelongitude-latitude points displayed within the longitude-latitude grapharea 240 may be points that have a latitude value between thelower-latitude limit 408 and the upper-latitude limit 404. Additionallyor alternatively, the displayed longitude-latitude points may have alongitude value between the lower-longitude limit 412 and theupper-longitude limit 416.

The longitude-latitude graph area 240 may include various displayedlongitude-latitude points. For example, the longitude-latitude graph 212may display one or more unhighlighted collections 284 oflongitude-latitude points, highlighted collections of longitude-latitudepoints (not shown), and/or selected collections 292 oflongitude-latitude points. In some cases, the one or more selectedcollections 292 of longitude-latitude points may include highlightedlongitude-latitude points. FIG. 4 shows the point marker 256 over apoint in a selected collection 292 of longitude-latitude points.

As shown in FIG. 4, the point marker 256 may be displayed within thelongitude-latitude graph 212. For example, a user may use an inputdevice to indicate where and/or in which graph the point marker 256 islocated. As noted above, if the point marker 256 is displayed within thelongitude-latitude graph 212, a tracking line latitude stamp 422 may bedisplayed. The tracking line latitude stamp 422 displays a latitudevalue associated with a longitude-latitude point corresponding to thepixel identified by the point marker 256. Additionally or alternatively,a tracking line longitude stamp 290 may be displayed. One or more pointmarker metadata stamps (e.g., the scalar stamp 274, the objectidentifier stamp 282, a latitude stamp, a longitude stamp, a time stamp)may be displayed, as described above.

An interface toggle 426 may be included to aid a user in interactingwith the longitude-latitude graph 212. For example, the interface toggle426 may allow a user to toggle a view of the longitude-latitude map onor off. The interface toggle 426 may be manipulated by a user from aninput device (e.g., function keys on a keyboard, a mouse, etc.). Asshown in FIG. 4, the longitude-latitude map is toggled on. Otherfunctionality is also possible.

FIG. 5 shows a detail view of an example scalar-time graph 208 that maybe a part of the visualization display 200 described in FIG. 2. Thescalar-time graph 208 may show one of a number of possible scalarvalues. For example, the scalar may refer to a magnitude, such as anintensity of reflected light. However, a number of other scalar valuesare possible, such as a size, a projected area, a temperature, a mass, aradar cross section, an altitude, an inclination, a delta-V, a timeuntil a certain event, a probability of a certain event, etc.

The scalar axis 248 may span from a lower-scalar limit 512 to anupper-scalar limit 516. Similarly, the second time axis 244 may spanfrom a lower-time limit 504 to an upper-time limit 508. The scalar-timepoints displayed within the scalar-time graph area 252 may be pointsthat have a scalar value between the lower-scalar limit 512 and theupper-scalar limit 516. Additionally or alternatively, the displayedscalar-time points may have a time value between the lower-time limit504 and the upper-time limit 508.

As shown in FIG. 5, the point marker 256 may be displayed within thescalar-time graph 208. As noted above, if the point marker 256 isdisplayed within the scalar-time graph 208, one or more metadata stampsmay be displayed. For example, the tracking line time stamp 298 mayindicate a time value of a scalar-time point corresponding to the pixelidentified by the point marker 256. Similarly, a tracking line scalarstamp (not shown) may indicate a scalar value of a scalar-time pointcorresponding to the pixel identified by the point marker 256Additionally or alternatively, one or more point marker metadata stamps(e.g., the scalar stamp 274, the object identifier stamp 282, a latitudestamp, a longitude stamp, a time stamp) may be displayed, as describedabove.

The scalar-time graph 208 may display one or more unhighlightedcollections 584 of scalar-time points, highlighted collections 584 ofscalar-time points (not shown), and/or selected collections 580 ofscalar-time points. As shown, the point marker 256 identifies a pixelassociated with a point in a selected collection 580 of scalar-timepoints. An interface toggle 522 may be included to aid a user ininteracting with the scalar-time graph 208. For example, the interfacetoggle 522 may allow a user to toggle which type(s) (e.g.,unhighlighted, highlighted, selected) points are displayed. Additionallyor alternatively, the interface toggle 522 may allow a user to togglebetween a stitching panel and a graph and/or to toggle which type ofscalar is displayed by the scalar-time graph 208. Other functionality isalso possible.

With reference generally to FIGS. 2-5, the system may allow a user tointeract with the visualization display 200 in a variety of beneficialways. For example, a user may be able to pan and zoom within one or moregraphs in the visualization display 200. Panning may be up, down, left,right, or any other direction along an axis. Zooming may include zoomingin and/or out. The user may give a panning input and/or a zooming inputvia an input device. The panning input and/or zooming input may comprisea scrolling of a mouse wheel, a click of a mouse, a pinch motion, aflick motion, a swipe motion, a tap, and/or any other input identifyinga pan or zoom action. The visualization display 200 may be configured toallow simultaneous manipulation of multiple graphs. For example, inresponse to a user input to pan or zoom the first time axis 220 or thesecond time axis 244, the system may set the lower-time limit 304 equalto the lower-time limit 504 and/or set the upper-time limit 308 equal tothe upper-time limit 508. Similarly, in response to a user input to panor zoom the first longitude axis 224 or the second longitude axis 236,the system may set the lower-longitude limit 312 equal to thelower-longitude limit 412 and set the upper-longitude limit 316 equal tothe upper-longitude limit 416.

A user may be able to set the upper and/or lower limits of a given axis.Additionally or alternatively, the user may be able to set axis spacing,axis intervals, axis labels, axis formatting, axis length, and or otheraspects associated with one or more axes. Once set, the system may beconfigured to automatically update that axis. In some embodiments, thesystem may be configured to automatically update a corresponding axis.For example, automatically updating a corresponding axis may includesetting a common alignment for both of the two axes, setting a commonlength for both of them, and/or disposing them parallel to one another.The first longitude axis 224 and second longitude axis 236 may becorresponding axes. Similarly, the first time axis 220 and second timeaxis 244 may be corresponding axes.

Zooming may be defined as changing a total span (e.g., a differencebetween an upper-axis limit and a lower-axis limit) of one or more axesin the visualization display 200. A single axis may be zoomed in or outby the user. A single graph (e.g., two perpendicular axes) may be zoomedin or out. However, the system may be configured to allow a user to zoomin and/or out on multiple axes and/or graphs simultaneously. Forexample, zooming in on the longitude-time graph 204 may adjust not onlythe first time axis 220 and first longitude axis 224, but it may adjustthe second time axis 244 as well.

Zooming and/or panning in one axis or one graph may affect which pointsare displayed in other graphs within the visualization display 200. Forexample, in an adjustment of the lower-time limit 304 or the upper-timelimit 308, the system may be configured to update the longitude-latitudegraph 212 to display pixels corresponding only to longitude-latitudepoints corresponding to a set of identifiers having a time identifierbetween the lower-time limit 304 and the upper-time limit 308.

Panning and/or zooming may be done within a graph or along an axis. Forexample, in response to a user input to pan or zoom along a length offirst time axis 220, the system may be configured to simultaneouslymodify one or more of the lower-time limit 304 and/or the upper-timelimit 308. In response to a user input to pan or zoom along a length ofsecond time axis 244, the system may be configured to simultaneouslymodify one or more of the lower-time limit 504 and/or the upper-timelimit 508. Additionally or alternatively, in response to a user input topan or zoom along a length of the first longitude axis 224, the systemmay be configured to simultaneously modify one or more of thelower-longitude limit 312 and/or the upper-longitude limit 316. Inresponse to a user input to pan or zoom along a length of the secondlongitude axis 236, the system may be configured to simultaneouslymodify one or more of the lower-longitude limit 412 and/or theupper-longitude limit 416. Additionally or alternatively, in response toa user input to pan or zoom along a length of the latitude axis 232, thesystem may be configured to simultaneously modify one or more of theupper-latitude limit 404 and/or the lower-latitude limit 408. Inresponse to a user input to pan or zoom along a length of the scalaraxis 248, the system may be configured to simultaneously modify one ormore of the lower-scalar limit 512 and the upper-scalar limit 516.

Further, in response to a user input to adjust the lower-longitude limit312 or the upper-longitude limit 316, the system may update thescalar-time graph 208 to display pixels corresponding only toscalar-time points corresponding to a set of identifiers having alongitude identifier between the lower-longitude limit 312 limit and theupper-longitude limit 316. Similarly, in response to a user input toadjust the upper-latitude limit 404 or the lower-latitude limit 408, thesystem may update one or more of the longitude-time graph 204 and/or thescalar-time graph 208 to display pixels corresponding only to respectivelongitude-time points and/or scalar-time points corresponding to a setof identifiers having a latitude identifier between the lower-longitudelimit 312 and the upper-longitude limit 316.

Moreover, in response to a user input to adjust the lower-scalar limit512 or the upper-scalar limit 516, the system may update one or more ofthe longitude-time graph 204 and the longitude-latitude graph 212 graphto display pixels corresponding only to respective longitude-time pointsand/or longitude-latitude points corresponding to a set of identifiershaving a scalar identifier between the lower-scalar limit 512 limit andthe upper-scalar limit 516.

As noted above, the system may be configured to store dozens ofpetabytes of data. This can provide a variety of challenges. One ofwhich is how the data are displayed in a way that is helpful to a humanuser. Accordingly, in certain embodiments, the visualization display 200may be configured to divide a graph (e.g., the longitude-time graph 204)into a plurality of pixels. Each pixel may represent a corresponding binof data. Each bin can be configured to store historical and/orcontemporary data as well as metadata.

In some cases, a single pixel may correspond to a bin containing dozens,hundreds, or even thousands of data sets corresponding to orbitalobjects. To aid a user in digesting such a large amount of data, thevisualization display 200 may be configured to display an indication ofthe amount of data (e.g., the number of objects, the number of sets ofobject identifiers) stored therein. For example, a user may use thepoint marker 256 to identify a pixel. The system can be configured todisplay a number of object identifiers (e.g., a number of unique objectidentifiers) between one and a total number of object identifiersassociated with the bin associated with the identified pixel. An objectidentifier can be any type of identifier of an orbital object. Theobject identifier may comprise one or more letters, numbers, symbols, orany combination of these.

In some designs, the system is configured to receive a selection from auser of a target object identifier. For example, the system maysequentially cycle (e.g., automatically, manually) through a display ofeach object identifier associated with the identified pixel (e.g., everysecond, every two seconds, in response to a user input, etc.). As adifferent example, the system may be configured to display a list ofobject identifiers from which a user may select the target objectidentifier. The system may be configured only to display unique objectidentifiers since many object identifiers in a single bin may beidentical. In some embodiments, the system may not display one or moreof the metadata stamps (e.g., the tracking line longitude stamp 290, thehorizontal tracking line 260, the object identifier stamp 282, thescalar stamp 274, etc.) until an object identifier has been selected. Incertain embodiments, the system displays metadata stamps for each uniqueobject identifier present in the bin. The visualization display 200 mayimplement a color scale or gray scale to provide information about thenumber of unique orbital object identifiers in a bin. For example, binswith more unique orbital object identifiers may correspond to lighterpixels while bins with fewer unique orbital object identifiers may bedarker. Bins with no orbital object identifiers may be black. Thissituation may arise, for example, when viewing a small portion (e.g.,zoomed in) of the data in a graph.

The system can be configured to identify one or more values (e.g., byvarious metadata time stamps described herein) associated with a defaultdata set. The point marker 256 is an example of an interface elementthat can identify values in the default data set. The default data setmay be determined based on one or more default rules. The defaultrule(s) may be based on a storage time (e.g., most recently stored), aview time (e.g., most recently viewed), a numerical value (e.g.,smallest latitude), an object identifier (e.g., earliest objectidentifier by alphabetical order), or any other default measure.

As a user moves the point marker 256, the system may automatically(e.g., in real-time) update the identified values (e.g., metadata timestamps) associated with the updated pixel corresponding to an updateddata set. The updated data set may be determined using the same ordifferent rules described above. The user may move the point marker 256over an updated pixel in a variety of ways, such as by mousing over thepixel using an input device (e.g., mouse), tapping on the pixel (e.g.,using a touchscreen), typing in information associated with the updatedpixel, or in any other way to identify a pixel.

It may be advantageous to allow a user to save one or more settingsassociated with the visualization display 200. For example, a user maywish to return at a later time to a point or set of points displayed bythe visualization display 200. This may be accomplished in a number ofways. For example, a user may be configured to bookmark one or morevalues associated with the target point (e.g., an object identifier, alongitude value, a time value, etc.). The system may store a list of theuser's bookmarks to allow for easy access at a future time. The systemmay be configured to store a set of points based, for example, on thepoints having a common object identifier. For example, multiple pointsmay correspond to the same object as it orbits the planet. Thus,multiple points in time and space may reference the same object. Theuser may be able to retrieve the set of points by inputting the objectidentifier (e.g., selecting it from a list, typing it in).

Additionally or alternatively, the system may be able to allow a user tosave a view of one or more graphs. For example, a user may be able tobookmark a particular view within the longitude-time graph 204.Accordingly, the system may associate with the bookmark stored valuesfor a bookmark-min longitude value (e.g., the lower-longitude limit312), a bookmark-max longitude value (e.g., the upper-longitude limit316), a bookmark-min time value (e.g., the lower-time limit 304), and/ora bookmark-max time value (e.g., the upper-time limit 308). Similarusage may be made for other values (e.g., a scalar value, an objectidentifier, a latitude). Points that satisfy these bookmark-min and/orbookmark-max values could be displayed by the system in response to auser selection of the associated bookmark.

Display Synchronization

One of the benefits of various embodiments described herein is theability of a user to quickly and easily view and digest an immenseamount of data containing variables in three, four, or more dimensions.To help a user visualize data containing higher-dimension values,various graphs of the visualization display 200 may be synchronized toeach other. FIGS. 6-9 illustrate various functionality associatedtherewith.

FIG. 6 shows a zoomed-in and panned view of visualization display 200 ofFIG. 2. As shown, the first time axis 220 spans from and updatedlower-time limit 304 to an updated upper-time limit 308. The first timeaxis 220 spans about fifteen weeks. Similarly, the first longitude axis224 has been updated to show a span of about 37 degrees between thelower-longitude limit 312 and the upper-longitude limit 316. The objectidentifier stamp 282 indicates the same object identifier shown in FIG.2. This indicates that the point marker 256 identifies a pixelassociated with the same object as is identified in FIG. 2. The trackingline longitude stamp 290 indicates a longitude of about 83.0019 W andthe tracking line time stamp 298 indicates a time of Jun. 17, 201708:10:51. As shown, the selected collection 280 of longitude-time pointsis associated with the pixel identified by the point marker 256. Otherunhighlighted collections 272 of longitude-time points are also shown,which are associated with the unhighlighted collections 284 oflongitude-latitude points.

The selected collection 280 of longitude-time points is similarlyassociated with the selected collection 292 of longitude-latitude pointsdisplayed in the longitude-latitude graph 212 as well as the selectedcollection 580 of scalar-time points displayed in the scalar-time graph208.

The visualization display 200 may further include a current time stamp610. The current time stamp 610 may indicate a current universal time,such as one tracking the coordinated universal time (UTC).

FIG. 7 shows the same view as FIG. 6 after the first longitude axis 224and the synchronized second longitude axis 236 have been zoomed in. Notethat the first longitude axis 224 and the second longitude axis 236 (aswell as the first time axis 220 and the second time axis 244) aresynchronized in this case, allowing for a seamless viewing experiencewhen viewing each of the graphs. Because the first longitude axis 224and the second longitude axis 236 are synchronized to each other, thescalar-time graph 208 has also been updated. The point marker 256identifies a slightly different pixel as compared to FIG. 6. As shown,both longitude axes 224, 236 span a little over a single degree.Moreover, as shown, the axis labels (and/or the associated hash marks)on the first longitude axis 224 have become omitted since the twolongitude axes 224, 236 are synchronized. Similarly, the two time axes220, 244 can be synchronized, in which case the axis labels (and/or theassociated hash marks) of the second time axis 244 may be omitted.

FIG. 8 shows the same view as FIG. 7 after the first time axis 220 andthe synchronized second time axis 244 have been zoomed in. Because thefirst time axis 220 and second time axis 244 are synchronized to eachother, the scalar-time graph 208 has also been updated. The point marker256 identifies a slightly different pixel as compared to either FIG. 6or FIG. 7.

FIG. 9 shows a zoomed-in and panned view of a longitude-time graph 204at a current time horizon. The current time horizon may be identified bya current time marker 922. The current time marker 922 may include aline and/or a descriptor, such as a “now” descriptor, as shown. Thefuture longitude-time area 914 and the future scalar-time area 918 donot include any display points corresponding to object data since thosetimes are later than the current time as indicated by the current timestamp 610. Data that has been received later than a threshold time fromthe current time may not be displayed yet. This delay may be due tolatency in the network (e.g., the network 144) or for some other reasonthat delays the system from receiving the data.

The image chip 268 in FIGS. 6-8 identifies an object image 270 while theimage chip 268 in FIG. 9 does not. The image chip 268 corresponds to aphotograph from which object data has been obtained associated with apixel identified by the point marker 256. The photographs shown in FIG.6-8 may identify the object image 270 received from actual telescopicimages. As noted, an image chip 268 may include a plurality of objectimages 270. In some embodiments, the image chip 268 identifies which ofthe plurality of object images 270 corresponds to the data associatedwith the pixel identified (e.g., by the point marker 256). For example,a marker may be displayed indicating a location of the object within theat least one photograph. The marker may comprise a circle, a box,crosshairs, a coloring, a flicker, or any other indication of an objectwithin a photograph. The user may identify the pixel associated with theobject image 270 in other ways described above.

Image chip 268 data may be received from one or more databases. Forexample, the system may receive the image chip 268 data from a databaseremote from the system. Additionally or alternatively, the data may bereceived from a database local to the system. The image chip 268 datamay be received via one or more pointers (e.g., hyperlinks) that pointto corresponding databases. For example, various image chip 268 data maybe stored on databases associated with the imager (e.g., telescope) fromwhich the data was first obtained.

The user may select one or more objects from an image chip 268 and acorresponding point or plurality of points may be indicated (e.g.,highlighted, supplied with a marker) on one or more of the graphs in thevisualization display 200. Additionally or alternatively, the user maybe able to select a point or plurality of points on one or more of thegraphs in the visualization display 200 and have one or more images(e.g., photo, video) displayed by the image chip 268 with associatedmarker. In some designs, the image chip 268 is configured to show avideo corresponding to multiple points within a graph in thevisualization display 200. The multiple points may comprise a commonobject identifier. In FIG. 9, because an identified pixel does notcorrespond to image data for a photograph, the blank image chip 926 doesnot display any photograph.

Tagging Interface

It may be useful to update data corresponding to the object data in thehistorical and/or contemporary databases. For example, it may be helpfulto add or remove an object identifier (e.g., object name) to one or morepoints. To this end, a tagging interface can be implemented in variousembodiments. FIGS. 10A-10D illustrate various aspects of embodiments ofthe system that include a tagging interface.

FIG. 10A shows a tagging interface comprising a stitching tool interface804 and an analysis plot interface 808. The tagging interface is shownalong with a longitude-time graph 204 and a longitude-latitude graph212. As shown, the stitching tool interface 804 may include a sourcetrack region designator 818 with corresponding source track region 820and/or an destination track region designator 826 with correspondingdestination track region 824. In some embodiments, the source trackregion designator 818 and/or destination track region designator 826 arenot included. The destination track region 824 may include one or moreof a stitch selector 828, a splice selector 832, an orbit selector 836,and/or a download selector 840. In response to the orbit selector 836,the system may be configured to calculate and/or display an aspect of anorbit of a selected object or plurality of objects. The stitching toolinterface 804 may further include an undo selector 834. The undoselector 834 may be represented by words “undo” and/or by a symbol(e.g., an arrow symbol). In response to a selection of the undo selector834, the system may undo a most recent user selection. In response to asequence of selections, the system may be configured to revert back asequence of actions in response to a sequence of previous userselections.

The analysis plot interface 808 may include one or more analysis plotinput selectors 848 and/or an interface toggle 266. The interface toggle266 may be selected by a user to toggle between a tagging interface andthe scalar-time graph 208 and/or display area 216. The analysis plotinterface 808 may include an analysis plot. The analysis plot maydisplay one or analysis points within a plot area. The analysis plot mayinclude a time axis and/or a scalar axis. The time axis may span aparticular number of days (e.g., five days, seven, days, ten days,etc.). The scalar axis may be determined based on a number of selectedpoints, such as a collection 816 of longitude-time destination points.

As shown in FIG. 10A, the collection 816 of longitude-time destinationpoints may be selected by a user. For example, the user may highlightone or more of the collection 816 of longitude-time destination points.As used herein, highlighting may include altering one or more of acolor, shading, intensity, and/or background. This may be achieved, forexample, by right-clicking on a mouse one of the points in thelongitude-time graph 204 and/or the longitude-latitude graph 212. Theright-click (or other user input) can cause the point marker 256 toidentify a pixel associated with object data. As shown in FIG. 10A, theuser has identified the collection 816 of longitude-time destinationpoints. The identified collection 816 of longitude-time destinationpoints may be highlighted (e.g., colored). The collection 816 oflongitude-time destination points corresponds to a collection 844 oflongitude-latitude destination points. The destination track identifier852 in the stitching tool interface 804 identifies the collection 816 oflongitude-time destination points as a destination track. The selectedpoints may correspond to the destination track analysis points 856displayed within the analysis plot interface 808.

FIG. 10B shows a selection by a user of a collection 868 of firstlongitude-time source points. The collection 868 of first longitude-timesource points may consist of a single point. As shown, the collection868 of first longitude-time source points is different from thecollection 816 of longitude-time destination points. The collection 868of first longitude-time source points may be highlighted (e.g.,differently from the highlighting of the collection 816 oflongitude-time destination points). The source track region 820 nowshows a first source track identifier 864 that has been selected. Acorresponding collection 872 of first longitude-latitude source pointsand/or a corresponding collection 860 of first source analysis pointsmay be plotted in their respective graph/plot.

FIG. 10C shows a selection by a user of a collection 880 of secondlongitude-time source points. The collection 880 of secondlongitude-time source points may consist of a single point. As shown,the collection 880 of second longitude-time source points is differentfrom either the collection 816 of longitude-time destination points orthe collection 868 of first longitude-time source points. Similarly, asshown, the highlighting of the collection 880 of second longitude-timesource points may be different from either the collection 816 oflongitude-time destination points or the collection 868 of firstlongitude-time source points. The second source track identifier 876indicates the additional selection of the collection 880 of secondlongitude-time source points. A corresponding collection 884 of secondlongitude-latitude source points and/or a corresponding collection 888of second source analysis points may be plotted in their respectivegraph/plot. A highlighted stitch selector 829 may indicate that theselected collections 868, 880 are ready to be stitched. It will be notedthat a single source track (as opposed to the two source tracks in thedisplayed example) may provide the highlighted stitch selector 829 aswell.

FIG. 10D shows the visualization display 200 of FIG. 10C after a userhas selected the stitch selector 828. Once the stitch selector 828 hasbeen selected by the user, the resulting new collection 892 oflongitude-time destination points comprise the original destination andsource track(s). A corresponding new collection 896 oflongitude-latitude destination points and/or a new collection 898 ofdestination analysis points may also be displayed. Accordingly, it maybe that no source tracks are indicated in the source track region 820.The destination track region 824 may continue to display an objectidentifier associated with the resulting destination track.

In this way, the tagging interface may allow a user to select adestination element comprising a first name identifier and a sourceelement comprising at least one of the plurality of pixels correspondingto longitude-time points comprising a second name identifier. Afterselecting the stitching selector, the display can be configured toindicate that the source element comprises the first name identifier. Insome designs, each of the destination element and source elementconsists of one or more points displayed by the system during the userselection of the stitching selector. In response to the user selection,the computer readable storage may be configured to associate a firstdata file comprising the first name identifier with a second data filecomprising the second name identifier.

A reverse process may be used to splice a collection of points intoseparate sets of points. For example, a user may be able to select acollection of source points as well as one or more splice points fromamong the source points. After selecting the splice selector 832, thesystem may be configured to remove and/or alter an object identifierassociated with the splice points relative to the source points.

For example, the system can be configured such that a user may be ableto select at least one pixel corresponding to at least onelongitude-time point comprising a first object identifier. The systemmay be configured to highlight a series of longitude-latitude pointscomprising an object identifier identical to the first objectidentifier. In response to a user selection of the splice selector, thesystem can be configured to distinguish a first set of one or morelongitude-time points from a second set of one or more longitude-timepoints on the visualization display 200.

The system can be configured to highlight one or more pixelscorresponding to a set of longitude-time points, for example, inresponse to a user input. The user input may comprise a selection of theone or more longitude-time points (e.g., via a selection of one or morepixels). The user input may include a mouse click, a double tap, a pinchmotion, a two-finger tap, a grouping (e.g., circling) motion, or someother input signifying a selection of points. In some embodiments, thesystem may highlight a series of points based on a user selection of afirst pixel. The system may be configured to highlight a series ofpixels comprising the first pixel. Each of the pixels in the series cancorrespond to longitude-time points comprising a common objectidentifier. Moreover, while longitude-time points have been used as anexample in FIGS. 10A-10D, other points (e.g., longitude-latitude points,analysis plot points) may be used for selecting and/or tagging (e.g.,stitching, splicing).

FIGS. 11-19 show various aspects of the system described herein.Elements having label numbers corresponding to elements describedelsewhere herein may have similar or identical functionality as thatdescribed as the corresponding elements.

FIG. 11 shows an example visualization display 200. As shown, thevisualization display 200 includes a longitude-time graph 204, alongitude-latitude graph 212, a scalar-time graph 208, and a displayarea 216. As shown, the longitude-time graph 204 includes a display of alongitude-time map 286. The longitude-latitude graph 212 also includes alongitude-latitude map 278. The longitude-time graph 204 also includes apoint marker 256, which is indicated by a vertical tracking line 264 anda horizontal tracking line 260. As shown, various collections 272, 276,280 of longitude-time points may be displayed. Corresponding collections284, 292, 288 of longitude-latitude points may be similarly displayed inthe longitude-latitude graph 212. Some vertical gridlines 294 andhorizontal gridlines 296 are also shown in each of the graphs 204, 208,212. Some of the labeled elements may appear in one or more of FIGS.12-19 as well, but for clarity the labels have not been included. Aperson of skill in the art would be able to identify elements describedherein within each Figure.

Autoselector

One of the many advantages of the systems described herein includes theability to track and/or predict space objects. The trajectory of a spaceobject can be extremely challenging to calculate and predict. Eachprediction may include a set of measurements, which can be variable intheir accuracy, precision, and/or dependability. For example,determining a position of the object in flight may require many imagesof the object using many optical sensors. Piecing the data from theseimages and arriving at an accurate and reliable position can beextremely difficult.

Despite the many challenges of capturing and allowing meaningful userinteractions with space objects, embodiments disclosed herein can allowa user and the system to work synergistically to help identify areaswhere certain data can be improved, modified, and/or removed ifnecessary. Such an interface combines access to an enormous dataset,direction to more interesting features and aspects of that dataset thata human user can understand, and often a user experience that allows forreal-time interaction with those features and aspects that is intuitiveand manageable. In certain embodiments, a user can work with the machineto identify, manipulate, and sort (e.g., combine) data about variousspace objects.

FIG. 20 shows an example user-selected first track (e.g., via a trackidentifier or track representation) and a system-predicted second track(e.g., via a system-predicted track identifier or track representation).A tagging interface is shown. One or more track representations (e.g.,lines) may represent a corresponding number of tracks. A track mayrepresent a path that an orbital object takes in space. One or morepoints or pixels may be used to indicate data points (e.g., timepoints)associated with an object's trajectory, position, time, etc. As shown,the first and second tracks may be displayed one on or more graphs. Forexample, a longitude-time graph may be shown together with alongitude-time graph (e.g., as described elsewhere herein). Additionallyor alternatively, one or more scalar-time plots may be included. Othergraphs/plots may be used, such as those described elsewhere herein.

FIG. 21 shows where second track is updated (e.g., to include additionaltracks). As shown in the photographs of FIGS. 20-21, for example, thefirst and/or the second tracks can include an indication of the “future”(e.g., below a “current time” line). A first track representation mayinclude points (e.g., longitude-time points) within a correspondinggraph (e.g., longitude-time graph). Each of the plurality oflongitude-time points can correspond to a set of identifiers having atime identifier between the lower-time limit and the upper-time limitand having a longitude identifier between the lower-longitude limit andthe upper-longitude limit. The first track representation can provide aview of at least a portion of the first track. Additional tracks may berepresented with corresponding track representations.

The display system may include a tagging interface that includes astitching selector (e.g., “Stitching Tool” in FIGS. 20-21). Thestitching selector may include certain functionality (e.g., buttons,interface design, etc.) of that described in relation to FIGS. 10A-10D,for example. In response to a user selection of a track representation,the display can indicate a selection (e.g., automatic, user-identified)of a different track representation corresponding to a second track. Thesystem may automatically determine that the second track representationbased on a determination that the second track is associated with thesame orbital object as the first track.

The second track representation may be displayed on one or more graphsdescribed herein. The system can highlight one or more of the firstand/or second track representations (e.g., based on a user selection ofthe corresponding track representation).

In certain embodiments, the system can update the display toprogressively highlight one or more additional track representations(e.g., after highlighting the first and/or second trackrepresentations). The system may update the display to automaticallyand/or progressively highlight each of the additional trackrepresentations. The delay may be between about 0.01 s to about 10 sbetween each of the highlights. The delay may depend on the density oftracks and/or the number of tracks in the viewable display. In responseto a user's suspend input, the system may suspend and/or stopprogressive highlighting of each of the additional trackrepresentations. A length of the delay between each of the highlightsmay depend on at least one of a density and/or a number of tracksdisplayed. The display may be configured to progressively highlight theadditional track representations based at least on a time identifierassociated with the additional track representations. The display mayprogressively highlight the additional track representations (e.g.,within the longitude-time graph) by receiving a user designation. Thedesignation may include one or more of a scroll indicator, a button, awheel, a switch, or any combination thereof. Additionally oralternatively, the display may deselect highlighting by receiving theuser designation.

As described in more detail herein, the system may be configured todetermine an orbital path of the orbital object. The orbital path may bedetermined over an orbital time period that includes a first time periodthat (i) overlaps the time period, (ii) precedes the time period, (iii)succeeds the time period, or (iv) any combination thereof. As shown inFIGS. 20-21, the orbital path may be shown on one, two, or more graphssimultaneously. For example, the orbital path may be shown on thelatitude-longitude graph and/or the longitude-time graphs. Othervariations are possible.

Image Stacking

The system can receive a plurality of photographs of space objectswithin a time domain. Each of the plurality of photographs cancorrespond to a latitude domain, a longitude domain, and/or a timestampwithin the time domain. Based on a selection (e.g., by a user), thesystem can receive image data derived from the plurality of photographs.In certain embodiments, the system may receive a user selection of alatitude range within the latitude domain, a longitude range within thelongitude domain, and/or a time range within the time domain. FIG. 22shows a photograph based on a user-selection of a latitude range, alongitude range, and a time range of set of photographs. Once selected,the display can show an object image 960 within the image chip 958.

In response to the user selection, the system may modify the image shownin the image chip 958. FIG. 23 shows an example modified photograph(e.g., based on a set of photographs) relative to the photograph showedin FIG. 22. The modification may be based on at least one of theplurality of photographs received by the system. As shown in FIG. 23,the display interface can generate a display of the 958. As shown in thephotographs of FIGS. 22-23, one or more of the space object'scharacteristics (e.g., location in photo, size, color, brightness, etc.)may be shown as being modified (e.g., the object may be removed from thephoto).

The modified image may be a combination (e.g., a summation, overlay,etc.) of two or more images of the plurality of photographs within theselected latitude range, longitude range, and time range. For example,the system may integrate (e.g., summate values of) the image dataderived from the plurality of photographs of space objects. For example,certain values (e.g., RGB values, color histogram values, imagehistogram values, brightness values, contrast values, contrast histogramvalues, etc.) may be added together and/or averaged across a pluralityof photographs to determine a final (e.g., integrated) value. One ofmore of the photographs may show a plurality of space objects eventhough FIGS. 22-23 show only a single space object.

The system can receive a user selection of an object shown in aphotograph and display a marker indicating a location of the objectwithin the photograph. The marker may include any marker, such as acircle, a box, and/or crosshairs. In some embodiments, a user can selecta time identifier and/or a name identifier associated with an object.Based on this selection, the system may display a marker indicating alocation of the object within the photograph.

The system can be configured to automatically identify one or moreobjects within the modified image. Such modification may includeincreasing or decreasing a brightness, a contrast, or a gamma value ofone or more photographs. Other changes may be made. For example, thesystem may reduce a characteristic of an object within at least one ofthe plurality of photographs. As another example, the system may removean object within at least one of the plurality of photographs, asfurther discussed below.

When reducing a characteristic of an object, the system can reduce abrightest of the object within the photograph. Additionally oralternatively, a larger object (e.g., the largest object in thephotograph) within the at least one of the plurality of photographs maybe obscured or removed. In some embodiments, the system is configured toreduce a characteristic of an object based on a location of the objectwithin the photograph. For example, a central object may be obscured orremoved from the photograph. The user may select the object and/or thesystem may automatically detect the object. Additionally oralternatively, the system may reduce a characteristic of the selectedobject, such as a brightness. Other objects may be removed from thephotograph or their visibility may be otherwise substantially reduced.

In some embodiments, the system develops each of image chips such that aspace object is disposed at a predetermined location of each image chipof a plurality of image chips. For example, the space object may bedisposed at or near a center of the image chip. This can allow a usermore convenient and intuitive visual access to the space object withinthe chip. Additionally or alternatively, this arrangement can allow forfewer mistakes by the system in identifying the space object, such aswhen modifying one or more characteristics thereof, as disclosed herein.

It may be further advantageous to dispose the space object within thesame predisposed location within the image chip within a particularrange of latitudes, longitudes, times, etc. For example, the spaceobject may be maintained at a center of each image chip even ascorresponding latitude and longitudes ranges change for each image chipof the plurality of image chips as the space object moves through space.The system may use this information to predict a position of the spaceobject position and/or an orbit of the space object orbit. The systemmay, based on the predicted space object's position and/or orbit,develop an image chip such that the predicted space object positionand/or the space object orbit position (e.g., in an image chip where theexpected position of the space object is located) is disposed at acenter of the image chip. Other configurations are possible.

Object Detection

It can be advantageous to be able to automatically and/or manuallyidentify objects in the photographs or image chips. For example, thesystem may be configured to detect one or more objects (e.g., additionalobjects) that may not have been previously detected by the system or auser.

Reference will now be made to FIGS. 24-25. FIG. 24 shows an indicationof a user-selected primary object 970 in a photograph and FIG. 25 showsan indication of a secondary object 972 detected by the system (e.g.,based on the user selection of the first object, based on an automaticdetection). As shown in the photographs of FIGS. 24-25, the primaryand/or secondary objects may be selected using user-inputted time and/orname identifiers. The system can automatically identify the primaryobject 970 in the photograph. In some embodiments, the system mayreceive a user selection of the secondary object 972 object in the atleast one of the plurality of photographs. The secondary object 972 maybe more visible in part because of modifications to the photographs, asdescribed herein. In response to the user selection of the secondaryobject 972 in the at least one of the plurality of photographs, derive asecond set of identifiers corresponding to the second orbital object.

A display a marker can be displayed to indicate a location of theprimary object 970 and/or the secondary object 972 (and/or otherobjects) within the photograph. The marker(s) 974, 976 can be one ormore of a circle, a box, crosshairs, and/or some other visual or audiblemarker. For example, as shown in FIG. 25, the secondary object selectionidentifier 976 may be a dotted-lined circle. The primary objectselection identifier 974 may be a different shape, size, color, etc. todistinguish it from the secondary object selection identifier 976.Various colors or highlights may additionally or alternatively beincluded to mark its location in the photograph.

In some embodiments, a user can select a time and/or name identifier tosignal to the system a particular location or other characteristic ofthe secondary object 972. The system can receive the time and/or nameidentifier display a marker indicating a location of the secondaryobject 972 within the at least one photograph. The user can enter thesecondary object's 972 via various input methods, such as a mouse,keyboard, eye gesture, hand gesture, and/or other indication.

In some embodiments, the system may be configured to derive a set ofidentifiers associated with the secondary object 972 to automaticallyidentify the secondary object 972 in one or more photographs. Forexample, the system may determine a particular contrast between anobject and a background. Additionally or alternatively, the system maydetermine that a primary object (e.g., the primary object 970) appearsto have an unusual shape, which may be an indication of another objectin the frame. Such a contrast may be more apparent, for example, if auser and/or the system automatically adjusts a parameter of the image,such as the image's brightness, contrast, gamma value, and/or othercharacteristic. As noted above, this modification may include modifyinga characteristic of the primary object 970 of the at least one of theplurality of photographs.

The system may receive the user input via two or more interface devices.For example, a combination of a keyboard, mouse, controller, headset,touch-interface, and/or other interfaces may be used.

Orbit Determination

As noted above, one of the many advantages of the systems describedherein includes the ability to track and/or predict space objects. Thetrajectory of a space object can be extremely challenging to calculateand predict. Yet, if determining a space object's position ischallenging, predicting the trajectory (e.g., orbit) of the object intothe future and/or based on limited data can often be even morecomplicated. Yet, in spite of these challenges, embodiments disclosedherein can accurately determine such trajectories and/or present thosedeterminations in a format that a user can readily understand andmanipulate. Such an interface combines access to an enormous dataset,direction to more interesting features and aspects of that dataset thata human user can understand, and often a user experience that allows forreal-time interaction with those features and aspects that is intuitiveand manageable. Indications of, and data on, an object's trajectory canbe indispensable to a user in certain circumstance. Such data may helpidentify future collisions, and having access to the data may helpprotect life and property.

Reference will now be made to FIGS. 26-29. FIG. 26 shows a plurality oftime points selected by user. FIG. 27 shows a track that extends bothinto the past and future. Tracks may include published orbit tracksand/or user-determined tracks. FIG. 28 shows an example of alongitude-time plot and a scalar-time plot showing same points. Asshown, two or more plots may be used to show the same plurality ofpoints and/or one or more of the same tracks. As shown in FIGS. 26-28,for example, a user may select timepoints by choosing a combination oftime, name, longitude, and/or latitude identifiers. FIG. 29 shows agraph of residuals (either between published and user-selected orbetween published and system-determined). For example, as shown, thescalar-time graph 208 may indicate the residual between thesystem-determined timepoints and/or track and another (e.g., published)corresponding track. The scalar-time graph 208 shown indicates that aresidual is near zero for some portions but deviates (e.g., to greaterthan 50) for other portions. Such a comparison can help the user and/orthe system to calibrate the accuracy of the system's determinations.Additionally or alternatively, the user and/or system may be better ableto determine the accuracy of the other corresponding track. As shown,the residual is represented as a sigma (“σ”) or other symbol. Theresidual may be shown as a difference, an average, a standard deviation,or other metric.

As shown, the system can receive a selection of a plurality oftimepoints (e.g., from a remote or local database, as described herein)corresponding to one or more orbital objects. Each timepoint may includesets of identifiers within a selected time period. For example, asshown, the point marker 256 indicates that a user has selected the trackrepresentation 940. Based on these timepoints, the system can determinean orbital path of an orbital object associated with the selectedplurality of timepoints, wherein the orbital path is determined over anorbital time period that includes a time period that (i) overlaps theselected time period, (ii) precedes the selected time period, (iii)succeeds the selected time period, or (iv) any combination thereof. Theselected time period generally spans from a lower-time limit to anupper-time limit that may be selected by a user or in certainimplementations by the system automatically. Based on the selection, thesystem can generate a display interface, such as the one shown in any ofFIGS. 26-29. The selected time period can determine one or more axes ofone of more graphs displayed, such as any of the graphs describedherein. The display can show an indication of the orbital path of theobject spanning the selected time period. This indication is representedas a predicted track representation 950 in FIGS. 27 and 29.

The selection of the timepoints may include a selection based one two ormore identifiers of those timepoints. This selection may help the systemidentify a space object of interest. For example, the selection may bebased on a selection of a time identifier and a name identifier,multiple time identifiers, multiple longitude identifiers, multiplelatitude identifiers, a combination of these, or some other combinationof identifiers.

Once selected, the system can display an indication of the orbital pathspanning a future-time period subsequent to the selected time period.Additionally or alternatively, the indication of the orbital path mayspan a prior-time period preceding the selected time period. As shown inFIG. 28, for example, an indication of the current time (e.g., the timethe user is using the display) may be displayed. The current time may beshown as a line traversing at least part of a longitude-time graphand/or a scalar-time graph, for example, as shown in FIG. 28.Additionally or alternatively, a time of a selected timepoint may bedisplayed. Such times can orient a user around which part of thedisplayed orbital path covers a future time period. As shown, forexample, in FIG. 29, the predicted track representation 950 may bedisplayed on a plurality of graphs simultaneously. Additionally oralternatively, the selected timepoints may be indicated on a pluralitygraphs.

Because the system in certain embodiments can predict the futureposition of the space object, the indicator of the current time may bedisplayed so as to indicate that the time period of the predicted trackrepresentation 950 spans a time later than the current time (e.g., the“future”).

It may be helpful for a user to compare a system-predicted path with athird-party published path (e.g., a path determined from a received pathequation or other symbolic representation). The system may, through anorbital path data interface for example, receive orbital path data fromone or more orbital path data sets (e.g., a third party data set, apreviously predicted data set of the disclosed systems). Each of thereceived orbital paths may be associated with the same orbital object.The system can then display, based on the received orbital path data, anindication of a received orbital path (e.g., from the third party)spanning the selected time period. This orbital path may be in additionto or instead of the predicted track representation 950, for example.

In some embodiments, the system can determine the received orbital pathbased on a comparison of corresponding name identifiers associated withthe received orbital path and the orbital path determined by the system.Because the orbital path data among the various predicted data may beslightly different, a comparison of the data may be helpful.Accordingly, the system may be able to compare the selected orbital pathwith the received orbital path and, based on the comparison, indicate aresult of the comparison. For example, the system may determine anddisplay a residual characteristic of the selected orbital path bydetermining a difference between a timepoint associated with theselected orbital path and a corresponding timepoint associated with thereceived orbital path.

Comparing the selected orbital path with the received orbital path mayinclude determining a difference between at least one identifier (e.g.,a time identifier, a latitude identifier, etc.) associated with theselected orbital path and a corresponding identifier of the receivedorbital path. The system may determine, for example, a residualcharacteristic (e.g., a level of accuracy or reliability) by calculatingan ascension and/or a declination based on the data. Otherconfigurations are possible.

Example Aspects

In a 1st aspect, a system displays measurements of objects in orbit. Thesystem can include a historical data interface configured to receivehistorical data of objects in orbit around a planet from a historicaldata set, the historical data comprising a time, a latitude, alongitude, and a scalar for each object; a real-time data interfaceconfigured to receive contemporary data of objects in orbit around aplanet from a contemporary data set, the contemporary data comprising atime, a latitude, a longitude, and a scalar for each object. Thecontemporary data can comprise data collected after the historical dataavailable from the historical data set; a non-transitorycomputer-readable medium comprising instructions executable by ahardware processor, wherein execution of the instructions by thehardware processor causes the system to generate a display interfacecomprising a longitude-time graph comprising: a longitude axis spanningfrom a lower-longitude limit to an upper-longitude limit, a time axisspanning from a lower-time limit to an upper-time limit; and a pluralityof pixels corresponding to longitude-time points within thelongitude-time graph, each of the plurality of longitude-time pointscorresponding to a data set comprising the historical data and thecontemporary data, wherein the data set comprises a time identifierbetween the lower-time limit and the upper-time limit and a longitudeidentifier between the lower-longitude limit and the upper-longitudelimit.

In a 2nd aspect, the system of aspect 1, wherein the display interfacefurther comprises a longitude-latitude graph comprising: a secondlongitude axis spanning from a second lower-longitude limit to a secondupper-longitude limit, a latitude axis spanning from a lower-latitudelimit to an upper-latitude limit; and a plurality of pixelscorresponding to longitude-latitude points within the longitude-latitudegraph, each of the plurality of longitude-latitude points correspondingto the data set comprising the historical data and the contemporarydata, wherein the data set comprises a latitude identifier between thelower-latitude limit and the upper-latitude limit and a longitudeidentifier between the second lower-longitude limit and the secondupper-longitude limit.

In a 3rd aspect, the system of any of aspects 1-2, wherein the displayinterface further comprises a scalar-time graph comprising: a scalaraxis spanning from a lower-scalar limit to an upper-scalar limit, asecond time axis spanning from a second lower-time limit to a secondupper-time limit; and a plurality of pixels corresponding to scalar-timepoints within the scalar-time graph, each of the plurality ofscalar-time points corresponding to the data set comprising thehistorical data and the contemporary data, wherein the data setcomprises a scalar identifier between the lower-scalar limit and theupper-scalar limit and a time identifier between the second lower-timelimit and the second upper-time limit.

In a 4th aspect, the system of any of aspects 1-3, wherein execution ofthe instructions by the hardware processor causes the system to: inresponse to user input to pan or zoom the time axis or the second timeaxis, set the lower-time limit equal to the second lower-time limit andset the upper-time limit equal to the second upper-time limit; and inresponse to user input to pan or zoom the longitude axis or the secondlongitude axis, set the lower-longitude limit equal to the secondlower-longitude limit and set the upper-longitude limit equal to thesecond upper-longitude limit.

In a 5th aspect, the system of any of aspects 1-3, wherein in responseto a user entry, the system updates a display of one or more axes,wherein updating the display of one or more axes comprises displayingone or more of an updated lower-time limit, an updated upper-time limit,an updated second lower-time limit, an updated second upper-time limit,an updated lower-longitude limit, an updated upper-longitude limit, anupdated second lower-longitude limit, an updated second upper-longitudelimit, an updated lower-latitude limit, an updated upper-latitude limit,an updated lower-scalar limit, or an updated upper-scalar limit.

In a 6th aspect, the system of any of aspects 1-3, wherein displayingupdated one or more of the axes is such that one or more of thefollowing are true: a difference between the updated upper-time limitand the updated lower-time limit is equal to a difference between theupper-time limit and the lower-time limit; a difference between theupdated second upper-time limit and the updated second lower-time limitis equal to a difference between the second upper-time limit and thesecond lower-time limit; a difference between the updatedupper-longitude limit and the updated lower-longitude limit is equal toa difference between the upper-longitude limit and the lower-longitudelimit; a difference between the updated second upper-longitude limit andthe updated second lower-longitude limit is equal to a differencebetween the second upper-longitude limit and the second lower-longitudelimit; a difference between the updated upper-latitude limit and theupdated lower-latitude limit is equal to a difference between theupper-latitude limit and the lower-latitude limit; or a differencebetween the updated upper-scalar limit and the updated lower-scalarlimit is equal to a difference between the upper-scalar limit and thelower-scalar limit.

In a 7th aspect, the system of aspect 1, wherein the display interfacefurther comprises at least a portion of a geographic map.

In a 8th aspect, the system of any of aspects 1-3, wherein thelongitude-time graph comprises the geographic map, wherein thelongitude-time points are superimposed on the geographic map, andwherein the longitude-time points and the geographic map are bothvisible to a viewer of the display interface.

In a 9th aspect, the system of aspect 1, wherein each pixel of theplurality of pixels represents a corresponding data bin, each data binstoring historical and/or contemporary data of a number of objectshaving a longitude between a bin-minimum longitude and a bin-maximumlongitude and having a time between a bin-minimum time and a bin-maximumtime.

In a 10th aspect, the system of aspect 9, wherein each pixel of theplurality of pixels comprises an indication of the number of objectsstored therein.

In a 11th aspect, the system of aspect 10, wherein the display interfacefurther comprises a point marker, the point marker identifying a firstpixel corresponding to a first longitude-time point within thelongitude-time graph, and wherein, in response to a user action, thepoint marker identifies a subsequent pixel corresponding to a subsequentlongitude-time point.

In a 12th aspect, the system of aspect 11, wherein the user actioncomprises mousing over the subsequent pixel.

In a 13th aspect, the system of any of aspects 11-12, wherein thedisplay interface further comprises one or more tracking linesindicating a location of the point marker.

In a 14th aspect, the system of aspect 13, wherein the display interfacefurther comprises a tracking line longitude stamp and a tracking linetime stamp, the tracking line longitude stamp indicating a longitudeassociated with the identified first pixel corresponding to the firstlongitude-time point, and the tracking line time stamp indicating a timeassociated with the identified first pixel.

In a 15th aspect, the system of any of aspects 1-14, wherein each of thehistorical data and contemporary data sets further comprises an objectidentifier for each object.

In a 16th aspect, the system of aspect 15, wherein in response to a usersave action, the system stores one or more objects as a bookmark, eachof the one or more objects of the bookmark comprising one or more of: acommon object identifier; a longitude between a bookmark-min longitudeand a bookmark-max longitude; a time between a bookmark-min time and abookmark-max time; a latitude between a bookmark-min latitude and abookmark-max latitude; and a scalar between a bookmark-min scalar and abookmark-max scalar.

In a 17th aspect, the system of any of aspects 15-16, wherein inresponse to a user save action, the system stores view-data associatedwith a view of the longitude-time graph, the view-data comprising dataassociated with the lower-time limit, the upper-time limit, thelower-longitude limit, and the upper-longitude limit.

In a 18th aspect, the system of any of aspects 1-17, wherein the scalarrepresents at least one of a magnitude, a projected area, a temperature,a mass, a radar cross section, an altitude, an inclination, a delta-v, atime until a certain event, or a probability of a certain event.

In a 19th aspect, the system of any of aspects 1-18, wherein thehistorical data set comprises data collected prior to a generation ofthe display interface.

In a 20th aspect, the system of any of aspects 1-19, wherein thecontemporary data comprises data collected after a generation of thedisplay interface, and wherein execution of the instructions by thehardware processor causes the system to update the display interfacewith pixels associated with the data collected after the generation ofthe display interface.

In a 21st aspect, the system of any of aspects 1-20, wherein thehistorical data comprises data collected over a period of time greaterthan one year.

In a 22nd aspect, a system for displaying measurements of objects inorbit, the system comprising: a computer readable storage mediumconfigured to communicate instructions for displaying one or moregraphs; a hardware processor in communication with the computer-readablestorage medium, wherein the instructions, when executed by the hardwareprocessor, are configured to cause the system to: receive a plurality ofsets of identifiers, wherein each set of identifiers corresponds to anorbital object and comprises: an object identifier; a time identifier; alatitude identifier; a longitude identifier; and a scalar identifier;and generate a display comprising: a longitude axis spanning from alower-longitude limit to an upper-longitude limit, a time axis spanningfrom a lower-time limit to an upper-time limit; and a plurality ofpixels corresponding to longitude-time points within the longitude-timegraph, each of the plurality of longitude-time points corresponding to adata set comprising the historical data and the contemporary data,wherein the data set comprises a time identifier between the lower-timelimit and the upper-time limit and a longitude identifier between thelower-longitude limit and the upper-longitude limit; and wherein eachpixel of the plurality of pixels represents a corresponding data bin,each data bin storing data of a number of objects having a longitudebetween a bin-minimum longitude and a bin-maximum longitude and having atime between a bin-minimum time and a bin-maximum time.

In a 23rd aspect, the system of aspect 22, wherein each pixel of theplurality of pixels comprises an indication of the number of objectsstored therein.

In a 24th aspect, the system of any of aspects 22-24, wherein thedisplay interface further comprises a point marker, the point markeridentifying a first pixel corresponding to a first longitude-time pointwithin the longitude-time graph, and wherein, in response to a useraction, the point marker identifies a subsequent pixel corresponding toa subsequent longitude-time point.

In a 25th aspect, the system of aspect 24, wherein the user actioncomprises mousing over the subsequent pixel.

In a 26th aspect, the system of any of aspects 24-25, wherein thedisplay interface further comprises one or more tracking linesindicating a location of the point marker.

In a 27th aspect, the system of aspect 26, wherein the display interfacefurther comprises a tracking line longitude stamp and a tracking linetime stamp, the tracking line longitude stamp indicating a longitudeassociated with the identified first pixel corresponding to the firstlongitude-time point, and the tracking line time stamp indicating a timeassociated with the identified first pixel.

In a 28th aspect, the system of any of aspects 24-27, wherein, inresponse to the user action, the display comprises a plurality of objectidentifiers.

In a 29th aspect, the system of aspect 28, wherein, in response to auser selection, the display comprises only one of the plurality ofobject identifiers.

In a 30th aspect, a system for presenting orbital object trackinginformation in synchronized graphs, the system comprising: a computerreadable storage configured to communicate instructions for displaying aplurality of graphs; a hardware processor in communication with thecomputer-readable storage, wherein the instructions, when executed bythe hardware processor, are configured to cause the system to: receive aplurality of sets of identifiers, each set of identifiers comprising: aname identifier; a time identifier; a latitude identifier; a longitudeidentifier; and a scalar identifier; generate a display of a pluralityof synchronized graphs, the display comprising: a longitude-time graphcomprising: a first longitude axis spanning from a first lower-longitudelimit to a first upper-longitude limit, a first time axis spanning froma first lower-time limit to a first upper-time limit; and a plurality ofpixels corresponding to longitude-time points within the longitude-timegraph, each of the plurality of longitude-time points corresponding to aset of identifiers having a time identifier between the first lower-timelimit and the first upper-time limit and having a longitude identifierbetween the first lower-longitude limit and the first upper-longitudelimit; a longitude-latitude graph comprising: a second longitude axisspanning from a second lower-longitude limit to a second upper-longitudelimit, a latitude axis spanning from a lower-latitude limit to anupper-latitude limit; and a plurality of pixels corresponding tolongitude-latitude points within the longitude-latitude graph, each ofthe plurality of longitude-latitude points corresponding to a set ofidentifiers having a latitude identifier between the lower-latitudelimit and the upper-latitude limit and having a longitude identifierbetween the second lower-longitude limit and the second upper-longitudelimit; a scalar-time graph comprising: a scalar axis spanning from alower-scalar limit to an upper-scalar limit, a second time axis spanningfrom a second lower-time limit to a second upper-time limit; and aplurality of pixels corresponding to scalar-time points within thescalar-time graph, each of the plurality of scalar-time pointscorresponding to a set of identifiers having a time identifier betweenthe second lower-time limit and the second upper-time limit and having ascalar identifier between the lower-scalar limit and the upper-scalarlimit; in response to a user input to adjust the first lower-longitudelimit or first upper-longitude limit, automatically update therespective second lower-longitude limit or second upper-longitude limit;in response to a user input to adjust the first lower-time limit orfirst upper-time limit, automatically update the respective secondlower-time limit or second upper-time limit.

In a 31st aspect, the system of aspect 30, wherein generating a displayof a plurality of graphs comprises: in response to user input to pan orzoom the first time axis or the second time axis, setting the firstlower-time limit equal to the second lower-time limit and setting thefirst upper-time limit equal to the second upper-time limit; and inresponse to user input to pan or zoom the first longitude axis or thesecond longitude axis, setting the first lower-longitude limit equal tothe second lower-longitude limit and setting the upper-longitude limitequal to the second upper-longitude limit.

In a 32nd aspect, the system of any of aspects 30-31, wherein thedisplay further comprises a point marker, the point marker identifying afirst pixel corresponding to a first longitude-time point within thelongitude-time graph, and wherein, in response to a user action, thepoint marker identifies a second pixel corresponding to a secondlongitude-time point.

In a 33rd aspect, the system of aspect 32, wherein the user actioncomprises mousing over the second pixel.

In a 34th aspect, the system of any of aspects 32-33, wherein thedisplay interface further comprises one or more tracking linesindicating a location of the point marker.

In a 35th aspect, the system of aspect 34, wherein the display interfacefurther comprises a first metadata stamp and a second metadata stamp,the first metadata stamp indicating a first metadata value associatedwith the identified first pixel corresponding to the firstlongitude-time point, and the second metadata stamp indicating a secondmetadata value associated with the identified first pixel.

In a 36th aspect, the system of aspect 35, wherein the first metadatavalue comprises a longitude identifier and the second metadata valuecomprises a time identifier.

In a 37th aspect, the system of any of aspects 32-36, wherein at leastone of the longitude-latitude graph and the scalar-time graph comprisesat least a portion of at least one of the one or more tracking lines.

In a 38th aspect, the system of any of aspects 32-37, wherein inresponse to a user selection, the system highlights a series of pixelscomprising the first pixel identified by the point marker, wherein eachof the pixels in the series corresponds to longitude-time pointscomprising a common name identifier.

In a 39th aspect, the system of aspect 38, wherein highlighting theseries of pixels comprises altering one or more of a color, shading,intensity, or background.

In a 40th aspect, the system of any of aspects 38-39, wherein inresponse to the user selection, the system highlights a series of pixelscorresponding to respective longitude-latitude points, wherein each ofthe pixels in the series corresponding to respective longitude-latitudepoints corresponds to longitude-latitude points comprising a common nameidentifier.

In a 41st aspect, the system of any of aspects 38-39, wherein inresponse to the user selection, the system highlights a series of pixelscorresponding to respective scalar-time points, wherein each of thepixels in the series corresponding to respective scalar-time pointscorresponds to scalar-time points comprising a common name identifier.

In a 42nd aspect, the system of any of aspects 30-41, wherein the scalarrepresents a magnitude.

In a 43rd aspect, the system of any of aspects 30-42, wherein, inresponse to a user input to adjust the first lower-time limit or thefirst upper-time limit, the system updates the longitude-latitude graphto display pixels corresponding only to longitude-latitude pointscorresponding to a set of identifiers having a time identifier betweenthe first lower-time limit and the first upper-time limit.

In a 44th aspect, the system of any of aspects 30-43, wherein, inresponse to a user input to adjust the first lower-longitude limit orthe first upper-longitude limit, the system updates the scalar-timegraph to display pixels corresponding only to scalar-time pointscorresponding to a set of identifiers having a longitude identifierbetween the first lower-longitude limit and the first upper-longitudelimit.

In a 45th aspect, the system of any of aspects 30-44, wherein, inresponse to a user input to adjust the lower-latitude limit or theupper-latitude limit, the system updates each of the longitude-timegraph and the scalar-time graph to display pixels corresponding only torespective longitude-time points or scalar-time points corresponding toa set of identifiers having a latitude identifier between thelower-latitude limit and the upper-latitude limit.

In a 46th aspect, the system of any of aspects 30-45, wherein, inresponse to a user input to adjust the lower-scalar limit or theupper-scalar limit, the system updates each of the longitude-time graphand the longitude-latitude graph to display pixels corresponding only torespective longitude-time points or longitude-latitude pointscorresponding to a set of identifiers having a scalar identifier betweenthe lower-scalar limit and the upper-scalar limit.

In a 47th aspect, the system of any of aspects 30-46, wherein: analignment of the first and second time axes are the same; a length ofthe first and second time axes are the same; the first and second timeaxes are parallel; an alignment of the first and second longitude axesare the same; a length of the first and second longitude axes are thesame; and the first and second longitude axes are parallel.

In a 48th aspect, the system of any of aspects 30-47, wherein generatinga display of a plurality of graphs comprises at least one of: inresponse to a user input to pan or zoom within an area defined by thelongitude-time graph, modifying simultaneously each of the firstlower-longitude limit, the first upper-longitude limit, the firstlower-time limit, and the first upper-time limit; in response to a userinput to pan or zoom within an area defined by the longitude-latitudegraph, modifying simultaneously each of the second lower-longitudelimit, the second upper-longitude limit, the lower-latitude limit, andthe upper-latitude limit; or in response to a user input to pan or zoomwithin an area defined by the scalar-time graph, modifyingsimultaneously each of the lower-scalar limit, the upper-scalar limit,the second lower-time limit, and the second upper-time limit.

In a 49th aspect, the system of aspect 48, wherein the user input to panor zoom comprises a scrolling of a mouse wheel, a click of a mouse, apinch motion, a flick motion, a swipe motion, or a tap.

In a 50th aspect, the system of any of aspects 30-49, wherein generatinga display of a plurality of graphs comprises at least one of: inresponse to a user input to pan or zoom along a length of the first timeaxis, modifying simultaneously each of the first lower-time limit andthe first upper-time limit; in response to a user input to pan or zoomalong a length of the second time axis, modifying simultaneously each ofthe second lower-time limit and the second upper-time limit; in responseto a user input to pan or zoom along a length of the first longitudeaxis, modifying simultaneously each of the first lower-longitude limitand the first upper-longitude limit; in response to a user input to panor zoom along a length of the second longitude axis, modifyingsimultaneously each of the second lower-longitude limit and the secondupper-longitude limit; in response to a user input to pan or zoom alonga length of the latitude axis, modifying simultaneously each of thelower-latitude limit and the upper-latitude limit; or in response to auser input to pan or zoom along a length of the scalar axis, modifyingsimultaneously each of the lower-scalar limit and the upper-scalarlimit.

In a 51st aspect, a system for tagging elements in a display of orbitalobject tracking information, the system comprising: a computer readablestorage configured to communicate instructions for displaying aplurality of graphs; a hardware processor in communication with thecomputer-readable storage, wherein the instructions, when executed bythe hardware processor, are configured to cause the system to: receive aplurality of sets of identifiers, wherein each set of identifierscorresponds to an orbital object and comprises: a name identifier; atime identifier; a latitude identifier; a longitude identifier; and ascalar identifier; and generate a display comprising: a longitude-timegraph comprising: a longitude axis spanning from a lower-longitude limitto an upper-longitude limit, a time axis spanning from a lower-timelimit to an upper-time limit; and a plurality of pixels corresponding tolongitude-time points within the longitude-time graph, each of theplurality of longitude-time points corresponding to a set of identifiershaving a time identifier between the lower-time limit and the upper-timelimit and having a longitude identifier between the lower-longitudelimit and the upper-longitude limit; a tagging interface comprising astitching selector, wherein in response to a user selection of: adestination element comprising a first name identifier, a source elementcomprising at least one of the plurality of pixels, the at least one ofthe plurality of pixels corresponding to longitude-time pointscomprising a second name identifier, and the stitching selector, thedisplay is configured to indicate that the source element comprises thefirst name identifier.

In a 52nd aspect, the system of aspect 51, wherein each of thedestination element and source element consists of one or more pointsdisplayed by the system during the user selection of the stitchingselector.

In a 53rd aspect, the system of any of aspects 51-52, wherein inresponse to the user selection, the computer readable storage associatesa first data file comprising the first name identifier with a seconddata file comprising the second name identifier.

In a 54th aspect, the system of any of aspects 51-52, wherein thedisplay further comprises a longitude-latitude graph comprising: asecond longitude axis spanning from a second lower-longitude limit to asecond upper-longitude limit, a latitude axis spanning from alower-latitude limit to an upper-latitude limit; and a plurality ofpixels corresponding to longitude-latitude points within thelongitude-latitude graph, each of the plurality of longitude-latitudepoints corresponding to a set of identifiers having a latitudeidentifier between the lower-latitude limit and the upper-latitude limitand having a longitude identifier between the second lower-longitudelimit and second upper-longitude limit.

In a 55th aspect, the system of aspect 54, wherein generating a displaycomprises: in response to user input to pan or zoom the longitude axisor the second longitude axis, setting the lower-longitude limit equal tothe second lower-longitude limit and setting the upper-longitude limitequal to the second upper-longitude limit.

In a 56th aspect, the system of aspect 55, wherein in response to theuser selection of the destination element comprising the first nameidentifier, the system highlights a series of pixels corresponding tolongitude-time points associated with the destination element, whereineach of the pixels in the series corresponds to longitude-time pointscomprising a common name identifier.

In a 57th aspect, the system of aspect 56, wherein highlighting theseries of pixels comprises altering one or more of a color, shading,intensity, or background.

In a 58th, the system of any of aspects 55-57, wherein in response tothe user selection of the destination element comprising the first nameidentifier, the system highlights a series of pixels corresponding tolongitude-latitude points associated with the destination element,wherein each of the pixels in the series corresponds tolongitude-latitude points comprising a common name identifier.

In a 59th aspect, the system of any of aspects 55-58, wherein inresponse to the user selection of the source element comprising thesecond name identifier, the system highlights one or more pixelscorresponding to one or more longitude-time points associated with thesource element, wherein each of the one or more highlighted pixelscorresponds to one or more longitude-time points comprising a commonname identifier.

In a 60th aspect, the system of any of aspects 55-59, wherein inresponse to the user selection of the source element comprising thesecond name identifier, the system highlights one or more pixelscorresponding to one or more longitude-latitude points associated withthe source element, wherein each of the one or more highlighted pixelscorresponds to one or more longitude-latitude points comprising a commonname identifier.

In a 61st aspect, the system of any of aspects 55-60, wherein thetagging interface further comprises a splice selector, wherein inresponse to a user selection of: at least one pixel corresponding to atleast one longitude-time point comprising a first name identifier, thesystem highlights a series of longitude-latitude points, each of thelongitude-latitude points in the series comprising an name identifieridentical to the first name identifier, and the splice selector, thedisplay is configured to distinguish a first set of one or morelongitude-time points from a second set of one or more longitude-timepoints.

In a 62nd aspect, the system of aspect 61, wherein in response to theuser selection of the splice selector, the display is further configuredto distinguish a first set of one or more longitude-latitude points froma second set of one or more longitude-latitude points.

In a 63rd aspect, the system of any of aspects 61-62, wherein each ofthe first set and second set consists of one or more points displayed bythe system during the user selection of the splice selector.

In a 64th, the system of any of aspects 51-63, wherein the displayfurther comprises an analysis plot comprising point plots correspondingto one or more scalar-time points.

In a 65th aspect, the system of any of aspects 51-64, wherein theplurality of sets of identifiers are derived from image datacorresponding to photographs of orbital objects.

In a 66th aspect, the system of any of aspects 51-65, further comprisinga real-time telescope data connection interface configured to receivethe image data from historical and contemporary data sets generated by anetwork of telescopes photographing a substantial portion of an orbit.

In a 67th aspect, a system for displaying image data derived fromphotographs of objects in orbit around a planet, the system comprising:a computer readable storage configured to communicate instructions fordisplaying a plurality of graphs; a hardware processor in communicationwith the computer-readable storage, wherein the instructions, whenexecuted by the hardware processor, are configured to cause the systemto: receive image data derived from a plurality of photographs ofobjects in orbit around the planet; receive a plurality of sets ofidentifiers, each of the sets associated with a photograph, a pluralityof identifiers of each set derived from the associated photograph,wherein each set of identifiers corresponds to an object in orbit andcomprises: a name identifier; a time identifier; a latitude identifier;a longitude identifier; and a scalar identifier; generate a displaycomprising: a longitude-time graph comprising: a longitude axis spanningfrom a lower-longitude limit to an upper-longitude limit, a time axisspanning from a lower-time limit to an upper-time limit; a plurality ofpixels corresponding to longitude-time points within the longitude-timegraph, each of the plurality of longitude-time points corresponding to aset of identifiers having a time identifier between the lower-time limitand the upper-time limit and having a longitude identifier between thelower-longitude limit and the upper-longitude limit; in response to auser selection of a time identifier and a name identifier, generate adisplay of at least one of the plurality of photographs.

In a 68th aspect, the system of aspect 67, wherein the instructions,when executed by the hardware processor, are configured to cause thesystem to receive the at least one of the plurality of photographs froma database remote from the system.

In a 69th aspect, the system of any of aspects 67-68, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to receive the at least one of the plurality ofphotographs from a database local to the system.

In a 70th aspect, the system of any of aspects 67-69, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to receive the at least one of the plurality ofphotographs via pointers, the at least one of the plurality ofphotographs stored in corresponding one or more databases.

In a 71st aspect, the system of any of aspects 67-70, wherein thedisplay further comprises a longitude-latitude graph comprising: asecond longitude axis spanning from a second lower-longitude limit to asecond upper-longitude limit, a latitude axis spanning from alower-latitude limit to an upper-latitude limit; and a plurality ofpixels corresponding to longitude-latitude points within thelongitude-latitude graph, each of the plurality of longitude-latitudepoints corresponding to a set of identifiers having a latitudeidentifier between the lower-latitude limit and the upper-latitude limitand having a longitude identifier between the second lower-longitudelimit and the second upper-longitude limit.

In a 72nd aspect, the system of any of aspects 67-71, wherein thedisplay further comprises a scalar-time graph comprising: a scalar axisspanning from a lower-scalar limit to an upper-scalar limit, a secondtime axis spanning from a second lower-time limit to a second upper-timelimit; and a plurality of pixels corresponding to scalar-time pointswithin the scalar-time graph, each of the plurality of scalar-timepoints corresponding to a set of identifiers having a time identifierbetween the second lower-time limit and the second upper-time limit andhaving a scalar identifier between the lower-scalar limit and theupper-scalar limit.

In a 73rd aspect, the system of any of aspects 67-72, wherein the scalarrepresents a magnitude.

In a 74th aspect, the system of any of aspects 67-73, wherein at leastone of the plurality of photographs shows a plurality of objects inorbit around the planet.

In a 75th aspect, the system of aspect 74, wherein the instructions,when executed by the hardware processor, are configured to cause thesystem to: receive a selection of an object shown in the at least onephotograph; and display a marker indicating a location of the objectwithin the at least one photograph.

In a 76th aspect, the system of aspect 75, wherein the marker comprisesat least one of a circle, a box, or crosshairs.

In a 77th aspect, the system of any of aspects 74-76, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to: receive a selection of a time identifier and a nameidentifier associated with an object; and display a marker indicating alocation of the object within the at least one photograph.

In a 78th aspect, a system for tagging elements in a display of orbitalobject tracking information, the system comprising: a computer readablestorage configured to communicate instructions for tagging elements in adisplay of orbital object tracking information; a hardware processor incommunication with the computer-readable storage, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to: receive a plurality of sets of identifiers, whereineach set of identifiers corresponds to an orbital object and comprises:a time identifier; a latitude identifier; a longitude identifier; and ascalar identifier; determine that a first track comprising a pluralityof the sets of identifiers is associated with the same orbital object;receive a name identifier associated with the first track; and generatea display comprising: a longitude-time graph comprising: a longitudeaxis spanning from a lower-longitude limit to an upper-longitude limit,a time axis spanning from a lower-time limit to an upper-time limit; anda first track representation comprising longitude-time points within thelongitude-time graph, each of the plurality of longitude-time pointscorresponding to a set of identifiers having a time identifier betweenthe lower-time limit and the upper-time limit and having a longitudeidentifier between the lower-longitude limit and the upper-longitudelimit, wherein the first track representation provides a view of atleast a portion of the first track; and a tagging interface comprising astitching selector, wherein in response to a user selection of the firsttrack representation, the display is configured to indicate an automaticselection of at least a second track representation corresponding to asecond track comprising a plurality of the sets of identifiers, thesecond track representation selected based on a determination that thesecond track is associated with the same orbital object as the firsttrack.

In a 79th aspect, the system of aspect 78, wherein the longitude-timegraph comprises at least a portion of the second track representation.

In a 80th aspect, the system of any of aspects 78-79, wherein thedisplay further comprises a longitude-latitude graph comprising: asecond longitude axis spanning from a second lower-longitude limit to asecond upper-longitude limit, a latitude axis spanning from alower-latitude limit to an upper-latitude limit; and alongitude-latitude track representation comprising longitude-latitudepoints within the longitude-latitude graph, each of the plurality oflongitude-latitude points corresponding to a set of identifiers having alatitude identifier between the lower-latitude limit and theupper-latitude limit and having a longitude identifier between thesecond lower-longitude limit and second upper-longitude limit, whereinthe longitude-latitude track representation provides a view of at leasta portion of the first track.

In a 81st aspect, the system of any of aspects 78-80, wherein theinstructions, when executed by the hardware processor, are configured toupdate the display to highlight the second track representation.

In a 82nd aspect, the system of aspect 81, wherein the instructions,when executed by the hardware processor, are configured to update thedisplay to progressively highlight one or more additional trackrepresentations after highlighting the second track representation.

In a 83rd aspect, the system of aspect 82, wherein the instructions,when executed by the hardware processor, are configured to update thedisplay automatically to progressively highlight each of the additionaltrack representations, wherein a delay of 0.01 s to 10 s is includedbetween each of the highlights.

In a 84th aspect, the system of aspect 83, wherein the instructions,when executed by the hardware processor, are configured to suspend, inresponse to a user's suspend input, the progressive highlighting of eachof the additional track representations.

In a 85th aspect, the system of aspect 84, wherein a length of the delaybetween each of the highlights depends on at least one of a density ornumber of tracks displayed.

In a 86th aspect, the system of aspect 85, wherein the instructions,when executed by the hardware processor, are configured to update thedisplay to progressively highlight the additional track representationsbased at least on a time identifier associated with the additional trackrepresentations.

In a 87th aspect, the system of any of aspects 85-86, wherein theinstructions, when executed by the hardware processor, are configured toupdate the display to progressively highlight the additional trackrepresentations within the longitude-time graph by receiving a userdesignation comprising a scroll indicator, a button, a wheel, a switch,or any combination thereof.

In a 88th aspect, the system of any of aspects 85-87, wherein theinstructions, when executed by the hardware processor, are configured toupdate the display to progressively deselect highlighted trackrepresentations within the longitude-time graph by receiving a userdesignation comprising a scroll indicator, a button, a wheel, a switch,or any combination thereof.

In a 89th aspect, the system of any of aspects 78-88, wherein thedisplay further comprises a scalar-time graph comprising: a scalar axisspanning from a lower-scalar limit to an upper-scalar limit, a time axisspanning from a lower-time limit to an upper-time limit; and ascalar-time track representation comprising scalar-time points withinthe scalar-time graph, each of the plurality of scalar-time pointscorresponding to a set of identifiers having a time identifier betweenthe lower-time limit and the upper-time limit and having a scalaridentifier between the second lower-scalar limit and second upper-scalarlimit, wherein the scalar-time track representation provides a view ofat least a portion of the first track.

In a 90th aspect, a computer-implemented method of tagging elements in adisplay of orbital object tracking information, the method comprising:receiving a plurality of sets of identifiers, wherein each set ofidentifiers corresponds to an orbital object and comprises: a timeidentifier; a latitude identifier; a longitude identifier; and a scalaridentifier; determining that a first track comprising a plurality of thesets of identifiers is associated with the same orbital object;receiving a name identifier associated with the first track; andgenerating a display comprising: a longitude-time graph comprising afirst track representation comprising longitude-time points within thelongitude-time graph, wherein the first track representation provides aview of at least a portion of the first track; and a tagging interfacecomprising a function selector; receiving a user selection of the firsttrack representation; in response to the user selection, determiningthat a second track comprising a plurality of the sets of identifiers isassociated with the same orbital object as the first track; andindicating an automatic selection of at least the second trackrepresentation corresponding to the second track.

In a 91st aspect, the method of aspect 90, further comprising updatingthe display to highlight the second track.

In a 92nd aspect, the method of any of aspects 90-91, wherein thefunction selector comprises a stitching selector, wherein in response toa user selection of the first track representation, the method comprisesindicating an automatic selection of at least a second trackrepresentation corresponding to a second track comprising a plurality ofthe sets of identifiers, the second track representation selected basedon a determination that the second track is associated with the sameorbital object as the first track.

In a 93rd aspect, the method of any of aspects 90-92, wherein thefunction selector comprises an orbit selector, and in response to a userselection of a track representation corresponding to an orbital objectand a time period, the method comprises: determining an orbital path ofthe orbital object, wherein the orbital path is determined over anorbital time period that includes a first time period that (i) overlapsthe time period, (ii) precedes the time period, (iii) succeeds the timeperiod, or (iv) any combination thereof, the first time period spanningfrom a lower-time limit to an upper-time limit; and generating a displayof an indication of the orbital path spanning at least the first timeperiod.

In a 94th aspect, a system for displaying image data derived fromphotographs of space objects, the system comprising: a computer readablestorage comprising instructions for displaying image data derived fromphotographs of space objects; a hardware processor in communication withthe computer-readable storage, wherein the instructions, when executedby the hardware processor, are configured to cause the system to:receive a plurality of photographs of space objects within a timedomain, each of the plurality of photographs corresponding to a latitudedomain, a longitude domain, and a timestamp within the time domain;receive image data derived from the plurality of photographs; receive auser selection of a latitude range within the latitude domain, alongitude range within the longitude domain, and a time range within thetime domain; in response to the user selection, modify an image based onat least one of the plurality of photographs and generate a display ofthe modified image.

In a 95th aspect, the system of aspect 94, wherein the instructions,when executed by the hardware processor, are configured to cause thesystem to generate a modified image from two or more images of theplurality of photographs within the selected latitude range, longituderange, and time range.

In a 96th aspect, the system of any of aspects 94-95, wherein the atleast one of the plurality of photographs shows a plurality of spaceobjects.

In a 97th aspect, the system of aspect 96, wherein the instructions,when executed by the hardware processor, are configured to cause thesystem to: receive a user selection of an object shown in the at leastone photograph; and display a marker indicating a location of the objectwithin the at least one photograph.

In a 98th aspect, the system of aspect 97, wherein the marker comprisesat least one of a circle, a box, or crosshairs.

In a 99th aspect, the system of any of aspects 96-98, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to: receive a user selection of a time identifier and aname identifier associated with an object; and display a markerindicating a location of the object within the at least one photograph.

In a 100th aspect, the system of any of aspects 94-99, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to integrate the image data derived from the pluralityof photographs of space objects.

In a 101st aspect, the system of any of aspects 94-100, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to sum image data from a plurality of photographsassociated with the time range.

In a 102nd aspect, the system of any of aspects 94-101, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to automatically identify one or more objects withinthe modified image.

In a 103rd aspect, the system of any of aspects 94-102, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to modify at least one of a brightness, contrast, orgamma of the at least one of the plurality of photographs.

In a 104th aspect, the system of any of aspects 94-103, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to reduce a characteristic of an object within at leastone of the plurality of photographs.

In a 105th aspect, the system of any of aspects 94-104, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to remove an object within at least one of theplurality of photographs.

In a 106th aspect, the system of aspect 105, wherein the removed objectcomprises at least one of a brightest object within the at least one ofthe plurality of photographs, a largest object within the at least oneof the plurality of photographs, or a central object within the at leastone of the plurality of photographs.

In a 107th aspect, the system of any of aspects 94-107, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to receive from a user a selection of an object withinthe at least one of the plurality of photographs.

In a 108th aspect, the system of aspect 107, wherein the instructions,when executed by the hardware processor, are configured to cause thesystem to reduce a characteristic of the selected object.

In a 109th aspect, the system of aspect 108, wherein the characteristicis a brightness of the selected object.

In a 110th aspect, the system of aspect 109, wherein the instructions,when executed by the hardware processor, are configured to cause thesystem to remove the selected object.

In a 111th aspect, the system of any of aspects 94-110, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to receive the at least one of the plurality ofphotographs from a database remote from the system.

In a 112th aspect, the system of any of aspects 94-111, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to receive the at least one of the plurality ofphotographs from a database local to the system.

In a 113th aspect, the system of any of aspects 94-112, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to receive the at least one of the plurality ofphotographs via pointers, the at least one of the plurality ofphotographs stored in corresponding one or more databases.

In a 114th aspect, the system of any of aspects 94-113, wherein thedisplay further comprises a longitude-latitude graph comprising: asecond longitude axis spanning from a second lower-longitude limit to asecond upper-longitude limit, a latitude axis spanning from alower-latitude limit to an upper-latitude limit; and a plurality ofpixels corresponding to longitude-latitude points within thelongitude-latitude graph, each of the plurality of longitude-latitudepoints corresponding to a set of identifiers having a latitudeidentifier between the lower-latitude limit and the upper-latitude limitand having a longitude identifier between the second lower-longitudelimit and the second upper-longitude limit.

In a 115th aspect, the system of any of aspects 94-114, wherein thedisplay further comprises a scalar-time graph comprising: a scalar axisspanning from a lower-scalar limit to an upper-scalar limit, a secondtime axis spanning from a second lower-time limit to a second upper-timelimit; and a plurality of pixels corresponding to scalar-time pointswithin the scalar-time graph, each of the plurality of scalar-timepoints corresponding to a set of identifiers having a time identifierbetween the second lower-time limit and the second upper-time limit andhaving a scalar identifier between the lower-scalar limit and theupper-scalar limit.

In a 116th aspect, the system of aspect 115, wherein the scalarrepresents a magnitude.

In a 117th aspect, the system of any of aspects 94-116, wherein thedisplay further comprises a longitude-time graph comprising: a longitudeaxis spanning from a lower-longitude limit to an upper-longitude limit,a time axis spanning from a lower-time limit to an upper-time limit; aplurality of pixels corresponding to longitude-time points within thelongitude-time graph, each of the plurality of longitude-time pointscorresponding to a set of identifiers having a time identifier betweenthe lower-time limit and the upper-time limit and having a longitudeidentifier between the lower-longitude limit and the upper-longitudelimit.

In a 118th aspect, a system for displaying space objects, the systemcomprising: a computer readable storage comprising instructions fordisplaying image data derived from photographs of space objects; ahardware processor in communication with the computer-readable storage,wherein the instructions, when executed by the hardware processor, areconfigured to cause the system to: receive a plurality of photographs ofspace objects within a time domain, each of the plurality of photographscorresponding to a latitude domain, a longitude domain, and a timestampwithin the time domain; derive image data from the plurality ofphotographs, the image data comprising a plurality of latitude rangeswithin the latitude domain, a plurality of longitude ranges within thelongitude domain, and a plurality of time points within the time domain;based on the derived image data, develop a plurality of image chips fromthe plurality of photographs, each of the plurality of image chipscomprising a corresponding latitude range within the latitude domain, alongitude range within the longitude domain, and a time point within thetime domain; in response to the user selection, display one or moreselected image chips of the plurality of image chips.

In a 119th aspect, the system of aspect 118, wherein the instructions,when executed by the hardware processor, are configured to develop eachof plurality of image chips such that a space object is disposed at acenter of each of the plurality of image chips.

In a 120th aspect, the system of aspect 119, wherein the space objectdisposed at the predetermined location of each of the plurality of imagechips is the same space object for each image chip.

In a 121st aspect, the system of aspect 119-120, wherein thepredetermined location of each of the plurality of image chips comprisesa center of the corresponding image chip.

In a 122nd aspect, the system of aspect 118-121, wherein theinstructions, when executed by the hardware processor, are configured todevelop the plurality of image chips from the plurality of photographssuch that the space object is maintained at a center of each image chipeven as corresponding latitude and longitudes ranges change for eachimage chip of the plurality of image chips as the space object movesthrough space.

In a 123rd aspect, the system of aspect 118-122, wherein theinstructions, when executed by the hardware processor, are configuredto: based on the derived image data, predict a location of at least oneof a space object position or a space object orbit; and based on atleast the predicted space object position or the space object orbit,develop an image chips such that at least one of the predicted spaceobject position or the space object orbit position space object isdisposed at a center of the image chip.

In a 124th aspect, a system for displaying image data derived fromphotographs of space objects, the system comprising: a computer readablestorage configured to communicate instructions for displaying image dataderived from a plurality of photographs of space objects; a hardwareprocessor in communication with the computer-readable storage, whereinthe instructions, when executed by the hardware processor, areconfigured to cause the system to: receive image data derived from theplurality of photographs; derive a plurality of sets of identifiers,each of the sets associated with a photograph, wherein each set ofidentifiers corresponds to a space object and comprises: a nameidentifier; a time identifier; a latitude identifier; a longitudeidentifier; and a scalar identifier; automatically identify a firstorbital object in at least one of the plurality of photographs; receivea user selection of a second orbital object in the at least one of theplurality of photographs; in response to the user selection of thesecond orbital object in the at least one of the plurality ofphotographs, derive a second set of identifiers corresponding to thesecond orbital object.

In a 125th aspect, the system of aspect 124, wherein the instructions,when executed by the hardware processor, are configured to cause thesystem to display a marker indicating a location of the second orbitalobject within the at least one photograph.

In a 126th aspect, the system of aspect 125, wherein the markercomprises at least one of a circle, a box, or crosshairs.

In a 127th aspect, the system of any of aspects 124-126, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to: receive a selection of a time identifier and a nameidentifier associated with the second orbital object; and display amarker indicating a location of the second orbital object within the atleast one photograph.

In a 128th aspect, the system of any of aspects 124-127, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to generate a display comprising a longitude-time graphcomprising: a longitude axis spanning from a lower-longitude limit to anupper-longitude limit, a time axis spanning from a lower-time limit toan upper-time limit; a plurality of pixels corresponding tolongitude-time points within the longitude-time graph, each of theplurality of longitude-time points corresponding to the second set ofidentifiers of the second orbital object, wherein the second set ofidentifiers has a time identifier between the lower-time limit and theupper-time limit and a longitude identifier between the lower-longitudelimit and the upper-longitude limit.

In a 129th aspect, the system of any of aspects 124-128, whereinderiving the second set of identifiers of the second orbital objectcomprises identifying, by the hardware processor, the second orbitalobject in the plurality of photographs.

In a 130th aspect, the system of any of aspects 124-129, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to transmit the second set of identifiers of the secondorbital object for storage remote from the system.

In a 131st aspect, the system of any of aspects 124-130, whereinreceiving the user selection of the second orbital object in the atleast one of the plurality of photographs comprises modifying at leastone of a brightness, a contrast, or a gamma of the at least one of theplurality of photographs.

In a 132nd aspect, the system of any of aspects 124-131, whereinreceiving the user selection of the second orbital object in the atleast one of the plurality of photographs comprises modifying acharacteristic of the first object of the at least one of the pluralityof photographs.

In a 133rd aspect, the system of any of aspects 124-132, whereinreceiving the user selection of the second orbital object in the atleast one of the plurality of photographs comprises receiving aplurality of inputs via at least two interface devices.

In a 134th aspect, the system of any of aspects 124-133, whereinreceiving the user selection of the second orbital object in the atleast one of the plurality of photographs comprises modifying acharacteristic of the selected second orbital object in the at least oneof the plurality of photographs.

In a 135th aspect, the system of any of aspects 124-134, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to receive the at least one of the plurality ofphotographs from a database remote from the system.

In a 136th aspect, the system of any of aspects 124-135, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to receive the at least one of the plurality ofphotographs from a database local to the system.

In a 137th aspect, the system of any of aspects 124-136, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to receive the at least one of the plurality ofphotographs via pointers, wherein the at least one of the plurality ofphotographs is stored in corresponding one or more databases.

In a 138th aspect, the system of any of aspects 124-138, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to generate a display comprising a longitude-latitudegraph comprising: a longitude axis spanning from a lower-longitude limitto an upper-longitude limit, a latitude axis spanning from alower-latitude limit to an upper-latitude limit; and a plurality ofpixels corresponding to longitude-latitude points within thelongitude-latitude graph, each of the plurality of longitude-latitudepoints corresponding to a set of identifiers having a latitudeidentifier between the lower-latitude limit and the upper-latitude limitand having a longitude identifier between the lower-longitude limit andthe upper-longitude limit.

In a 139th aspect, the system of any of aspects 124-139, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to generate a display comprising a scalar-time graphcomprising: a scalar axis spanning from a lower-scalar limit to anupper-scalar limit, a time axis spanning from a lower-time limit to anupper-time limit; and a plurality of pixels corresponding to scalar-timepoints within the scalar-time graph, each of the plurality ofscalar-time points corresponding to a set of identifiers having a timeidentifier between the lower-time limit and the upper-time limit andhaving a scalar identifier between the lower-scalar limit and theupper-scalar limit.

In a 140th aspect, the system of aspect 139, wherein the scalarrepresents a magnitude.

In a 141st aspect, the system of any of aspects 124-140, furthercomprising: a historical data interface configured to receive historicaldata of space objects from a historical data set; and a real-time datainterface configured to receive contemporary data of space objects froma contemporary data set, wherein the contemporary data comprises datacollected after the historical data available from the historical dataset; wherein the plurality of sets of identifiers are received via oneor both of the historical or real-time data interfaces.

In a 142nd aspect, a system for determining and displaying an orbit ofan orbital object using observations of the orbital object collectedover a selected time period, the system comprising: a computer readablestorage configured to communicate instructions for displaying one ormore graphs; an orbital object data interface configured to receiveorbital object data from a data set covering at least the selected timeperiod, the orbital object data comprising a time, a latitude, alongitude, and a scalar for the orbital object; and a hardware processorin communication with the computer-readable storage, wherein theinstructions, when executed by the hardware processor, are configured tocause the system to: receive a plurality of sets of identifiers, whereineach set of identifiers corresponds to an orbital object and comprises:a name identifier; a time identifier; a latitude identifier; and alongitude identifier; receive a selection of a plurality of timepointscorresponding to an orbital object, wherein the selection of theplurality of timepoints comprises sets of identifiers within theselected time period; determine an orbital path of the orbital objectassociated with the selected plurality of timepoints, wherein theorbital path is determined over an orbital time period that includes afirst time period that (i) overlaps the selected time period, (ii)precedes the selected time period, (iii) succeeds the selected timeperiod, or (iv) any combination thereof, the first time period spanningfrom a lower-time limit to an upper-time limit; and generate a displayinterface comprising: a longitude-time graph comprising: a longitudeaxis spanning from a lower-longitude limit to an upper-longitude limit,a time axis spanning from the lower-time limit to the upper-time limit;and an indication of the orbital path spanning at least the first timeperiod.

In a 143rd aspect, the system of aspect 142, wherein the displayinterface further comprises a longitude-latitude graph comprising: asecond longitude axis spanning from a second lower-longitude limit to asecond upper-longitude limit, a latitude axis spanning from alower-latitude limit to an upper-latitude limit; and a plurality ofpixels corresponding to longitude-latitude points within thelongitude-latitude graph, each of the plurality of longitude-latitudepoints corresponding to a set of identifiers having a latitudeidentifier between the lower-latitude limit and the upper-latitude limitand having a longitude identifier between the second lower-longitudelimit and the second upper-longitude limit.

In a 144th aspect, the system of any of aspects 142-143, wherein thedisplay interface further comprises a scalar-time graph comprising: ascalar axis spanning from a lower-scalar limit to an upper-scalar limit,a second time axis spanning from a second lower-time limit to a secondupper-time limit; and a plurality of pixels corresponding to scalar-timepoints within the scalar-time graph, each of the plurality ofscalar-time points corresponding to a set of identifiers having a timeidentifier between the second lower-time limit and the second upper-timelimit and having a scalar identifier between the lower-scalar limit andthe upper-scalar limit.

In a 145th aspect, the system of any of aspects 142-144, wherein theselection of the plurality of timepoints comprise a time identifier anda name identifier.

In a 146th aspect, the system of any of aspects 142-145, wherein theselection of the plurality of timepoints comprise a plurality of timeidentifiers.

In a 147th aspect, the system of any of aspects 142-146, wherein theselection of the plurality of timepoints comprise a plurality oflongitude identifiers.

In a 148th aspect, the system of any of aspects 142-147, wherein theselection of the plurality of timepoints comprise a plurality oflatitude identifiers.

In a 149th aspect, the system of any of aspects 142-148, whereinexecution of the instructions by the hardware processor causes thesystem to display an indication of the orbital path spanning afuture-time period subsequent to the selected time period.

In a 150th aspect, the system of any of aspects 142-149, whereinexecution of the instructions by the hardware processor causes thesystem to display an indication of the orbital path spanning aprior-time period preceding the selected time period.

In a 151st aspect, the system of any of aspects 142-150, the displayfurther comprising an indicator of the current time.

In a 152nd aspect, the system of aspect 151, wherein the indicator ofthe current time comprises a line traversing at least part of thelongitude-time graph.

In a 153rd aspect, the system of any of aspects 151-152, wherein theindicator of the current time comprises a line traversing at least partof the scalar-time graph.

In a 154th aspect, the system of any of aspects 151-153, whereinexecution of the instructions by the hardware processor causes thesystem to display the indication of the orbital path in relation to theindicator of the current time so as to indicate that the first timeperiod spans a time later than the current time.

In a 155th aspect, the system of any of aspects 151-154, whereinexecution of the instructions by the hardware processor causes thesystem to display the indication of the orbital path in relation to theindicator of the current time so as to indicate that the first timeperiod spans a time prior to the current time.

In a 156th aspect, the system of any of aspects 142-155, furthercomprising an orbital path data interface configured to receive orbitalpath data from an orbital path data set, the orbital path datacomprising a plurality of received orbital paths, each of the pluralityof received orbital paths being associated with an orbital objectcorresponding to a plurality of timepoints, and wherein execution of theinstructions by the hardware processor causes the system to display,based on the received orbital path data, an indication of a receivedorbital path spanning at least the first time period.

In a 157th aspect, the system of aspect 156, wherein execution of theinstructions by the hardware processor causes the system to determinethe received orbital path based on a comparison of corresponding nameidentifiers associated with the received orbital path and the firstorbital path.

In a 158th aspect, the system of aspect 157, wherein execution of theinstructions by the hardware processor causes the system to: compare thefirst orbital path with the received orbital path; and based on thecomparison, indicate a result of the comparison.

In a 159th aspect, the system of aspect 158, wherein comparing the firstorbital path with the received orbital path comprises determining adifference between at least one identifier associated with the firstorbital path and a corresponding identifier of the received orbitalpath.

In a 160th aspect, the system of any of aspects 158-159, whereinexecution of the instructions by the hardware processor causes thesystem to determine a difference between at least one identifierassociated with the first orbital path and a corresponding identifier ofthe received orbital path.

In a 161st aspect, the system of any of aspects 158-160, whereinexecution of the instructions by the hardware processor causes thesystem to determine a residual characteristic of the first orbital pathby determining a difference between a timepoint associated with thefirst orbital path and a corresponding timepoint associated with thereceived orbital path.

In a 162nd aspect, the system of aspect 161, wherein determining thedifference between a timepoint associated with the first orbital pathand a corresponding timepoint associated with the received orbital pathcomprises calculating one or more of an ascension or a declination.

In a 163rd aspect, a system for displaying measurements of spaceobjects, the system comprising: a computer readable storage mediumconfigured to communicate instructions for displaying one or moregraphs; an orbital object data interface configured to receive orbitalobject data from a data set covering at least the selected time period,the orbital object data comprising a time, a latitude, a longitude, anda scalar for an orbital object; a hardware processor in communicationwith the computer-readable storage medium, wherein the instructions,when executed by the hardware processor, are configured to cause thesystem to: receive a plurality of sets of identifiers, wherein each setof identifiers corresponds to the orbital object and comprises: anobject identifier; a time identifier; a latitude identifier; and alongitude identifier; receive a track comprising a plurality of the setsof identifiers associated with the orbital object; display alongitude-time graph comprising: a longitude axis spanning from alower-longitude limit to an upper-longitude limit, a time axis spanningfrom a lower-time limit to an upper-time limit; and a trackrepresentation comprising longitude-time points within thelongitude-time graph, each of the plurality of longitude-time pointscorresponding to a set of identifiers having a time identifier betweenthe lower-time limit and the upper-time limit and having a longitudeidentifier between the lower-longitude limit and the upper-longitudelimit, wherein the track representation provides a view of at least aportion of the track; and in response to a user selection of the trackand receipt of a user instruction to determine an orbit, display anorbit representation on the longitude-time graph by: determining anorbit of the orbital object using the selected track during a timeperiod comprising a time after or before the current time; andoverlaying the orbit representation corresponding to the determinedorbit on the longitude-time graph.

In a 164th aspect, the system of aspect 163, wherein execution of theinstructions by the hardware processor causes the system to display theorbit representation on the longitude-time graph, on alongitude-latitude graph, or on a combination of graphs.

In a 165th aspect, the system of any of aspects 163-164, the displayfurther comprising an indicator of the current time.

In a 166th aspect, the system of any of aspects 163-165, wherein thedisplay interface further comprises a scalar-time graph comprising: ascalar axis spanning from a lower-scalar limit to an upper-scalar limit,a second time axis spanning from a second lower-time limit to a secondupper-time limit; and a plurality of pixels corresponding to scalar-timepoints within the scalar-time graph, each of the plurality ofscalar-time points corresponding to a set of identifiers having a timeidentifier between the second lower-time limit and the second upper-timelimit and having a scalar identifier between the lower-scalar limit andthe upper-scalar limit.

In a 167th aspect, the system of any of aspects 163-166, wherein theindicator of the current time comprises a line traversing at least partof the longitude-time graph, the scalar-time graph, or both.

CONCLUSION

Reference throughout this specification to “some embodiments” or “anembodiment” means that a particular feature, structure or characteristicdescribed in connection with the embodiment is included in at least someembodiments. Thus, appearances of the phrases “in some embodiments” or“in an embodiment” in various places throughout this specification arenot necessarily all referring to the same embodiment and may refer toone or more of the same or different embodiments. Furthermore, theparticular features, structures or characteristics may be combined inany suitable manner, as would be apparent to one of ordinary skill inthe art from this disclosure, in one or more embodiments.

As used in this application, the terms “comprising,” “including,”“having,” and the like are synonymous and are used inclusively, in anopen-ended fashion, and do not exclude additional elements, features,acts, operations, and so forth. Also, the term “or” is used in itsinclusive sense (and not in its exclusive sense) so that when used, forexample, to connect a list of elements, the term “or” means one, some,or all of the elements in the list.

Similarly, it should be appreciated that in the above description ofembodiments, various features are sometimes grouped together in a singleembodiment, figure, or description thereof for the purpose ofstreamlining the disclosure and aiding in the understanding of one ormore of the various inventive aspects. This method of disclosure,however, is not to be interpreted as reflecting an intention that anyclaim require more features than are expressly recited in that claim.Rather, inventive aspects lie in a combination of fewer than allfeatures of any single foregoing disclosed embodiment. Accordingly, nofeature or group of features is necessary or indispensable to eachembodiment.

Embodiments of the disclosed systems and methods may be used and/orimplemented with local and/or remote devices, components, and/ormodules. The term “remote” may include devices, components, and/ormodules not stored locally, for example, not accessible via a local bus.Thus, a remote device may include a device which is physically locatedin the same room and connected via a device such as a switch or a localarea network. In other situations, a remote device may also be locatedin a separate geographic area, such as, for example, in a differentlocation, building, city, country, and so forth.

Methods and processes described herein may be embodied in, and partiallyor fully automated via, software code modules executed by one or moregeneral and/or special purpose computers. The word “module” refers tologic embodied in hardware and/or firmware, or to a collection ofsoftware instructions, possibly having entry and exit points, written ina programming language, such as, for example, C or C++. A softwaremodule may be compiled and linked into an executable program, installedin a dynamically linked library, or may be written in an interpretedprogramming language such as, for example, BASIC, Perl, or Python. Itwill be appreciated that software modules may be callable from othermodules or from themselves, and/or may be invoked in response todetected events or interrupts. Software instructions may be embedded infirmware, such as an erasable programmable read-only memory (EPROM). Itwill be further appreciated that hardware modules may comprise connectedlogic units, such as gates and flip-flops, and/or may compriseprogrammable units, such as programmable gate arrays, applicationspecific integrated circuits, and/or processors. The modules describedherein may be implemented as software modules, or may be represented inhardware and/or firmware. Moreover, although in some embodiments amodule may be separately compiled, in other embodiments a module mayrepresent a subset of instructions of a separately compiled program, andmay not have an interface available to other logical program units.

In certain embodiments, code modules may be implemented and/or stored inany type of non-transitory computer-readable medium or othernon-transitory computer storage device. In some systems, data (and/ormetadata) input to the system, data generated by the system, and/or dataused by the system can be stored in any type of computer datarepository, such as a relational database and/or flat file system. Anyof the systems, methods, and processes described herein may include aninterface configured to permit interaction with patients, health carepractitioners, administrators, other systems, components, programs, andso forth.

A number of applications, publications, and external documents may beincorporated by reference herein. Any conflict or contradiction betweena statement in the body text of this specification and a statement inany of the incorporated documents is to be resolved in favor of thestatement in the body text.

Although described in the illustrative context of certain preferredembodiments and examples, it will be understood by those skilled in theart that the disclosure extends beyond the specifically describedembodiments to other alternative embodiments and/or uses and obviousmodifications and equivalents. Thus, it is intended that the scope ofthe example embodiments which follow should not be limited by theparticular embodiments described above.

What is claimed:
 1. A system for displaying image data derived fromphotographs of objects in orbit around a planet, the system comprising:a non-transitory computer readable storage configured to communicateinstructions for displaying a plurality of graphs; a hardware processorin communication with the non-transitory computer-readable storage,wherein the instructions, when executed by the hardware processor, areconfigured to cause the system to: receive image data derived from aplurality of photographs of objects in orbit around the planet; receivea plurality of sets of identifiers, each of the sets associated with aphotograph, a plurality of identifiers of each set derived from theassociated photograph, wherein each set of identifiers corresponds to anobject in orbit and comprises: a name identifier; a time identifier; alatitude identifier; a longitude identifier; and a scalar identifier;generate a display comprising: a longitude-time graph comprising: alongitude axis spanning from a lower-longitude limit to anupper-longitude limit, a time axis spanning from a lower-time limit toan upper-time limit; a plurality of pixels corresponding tolongitude-time points within the longitude-time graph, each of theplurality of longitude-time points corresponding to a set of identifiershaving a time identifier between the lower-time limit and the upper-timelimit and having a longitude identifier between the lower-longitudelimit and the upper-longitude limit; in response to a user selection ofa time identifier and a name identifier, generate a display of at leastone of the plurality of photographs.
 2. The system of claim 1, whereinthe instructions, when executed by the hardware processor, areconfigured to cause the system to receive the at least one of theplurality of photographs from a database remote from the system.
 3. Thesystem of claim 1, wherein the instructions, when executed by thehardware processor, are configured to cause the system to receive the atleast one of the plurality of photographs from a database local to thesystem.
 4. The system of claim 1, wherein the instructions, whenexecuted by the hardware processor, are configured to cause the systemto receive the at least one of the plurality of photographs viapointers, the at least one of the plurality of photographs stored incorresponding one or more databases.
 5. The system of claim 1, whereinthe display further comprises a longitude-latitude graph comprising: asecond longitude axis spanning from a second lower-longitude limit to asecond upper-longitude limit, a latitude axis spanning from alower-latitude limit to an upper-latitude limit; and a plurality ofpixels corresponding to longitude-latitude points within thelongitude-latitude graph, each of the plurality of longitude-latitudepoints corresponding to a set of identifiers having a latitudeidentifier between the lower-latitude limit and the upper-latitude limitand having a longitude identifier between the second lower-longitudelimit and the second upper-longitude limit.
 6. The system of claim 1,wherein the display further comprises a scalar-time graph comprising: ascalar axis spanning from a lower-scalar limit to an upper-scalar limit,a second time axis spanning from a second lower-time limit to a secondupper-time limit; and a plurality of pixels corresponding to scalar-timepoints within the scalar-time graph, each of the plurality ofscalar-time points corresponding to a set of identifiers having a timeidentifier between the second lower-time limit and the second upper-timelimit and having a scalar identifier between the lower-scalar limit andthe upper-scalar limit.
 7. The system of claim 1, wherein the scalarrepresents a magnitude.
 8. The system of claim 1, wherein at least oneof the plurality of photographs shows a plurality of objects in orbitaround the planet.
 9. The system of claim 8, wherein the instructions,when executed by the hardware processor, are configured to cause thesystem to: receive a selection an object shown in the at least onephotograph; and display a marker indicating a location of the objectwithin the at least one photograph.
 10. The system of claim 9, whereinthe marker comprises at least one of a circle, a box, or crosshairs. 11.The system of claim 8, wherein the instructions, when executed by thehardware processor, are configured to cause the system to: receive aselection of a time identifier and a name identifier associated with anobject; and display a marker indicating a location of the object withinthe at least one photograph.